Welcome to the MacNN Forums.

MacGorilla · Jan 1, 2004, 04:03 PM

Okay, here is my set etup. I'm sharing my Cable Modem via my mac.

Built in Ethernet has cable modem.
I added two PCI network cards, D links. The problem is with the computers connected to the dlinks. If one is on, it'll boot the other. Weird, I can't figure out why.

kampl · Jan 1, 2004, 09:25 PM

Originally posted by MacGorilla:
Okay, here is my set etup. I'm sharing my Cable Modem via my mac.

Built in Ethernet has cable modem.
I added two PCI network cards, D links. The problem is with the computers connected to the dlinks. If one is on, it'll boot the other. Weird, I can't figure out why.

I don't think I understand the question. Can you elaborate a little more on the problem?

MacGorilla · Jan 1, 2004, 10:13 PM

I have a cable modem plugged into the built ethernet port. I get my ip via DHCP. All this good,

In PCI slot 5 I have a d link network card. It has an ip of 192. 168.0.7

In PCI slot 4 I also have a d link ethernet card with an ip 192.168. 0.8

One card to connect to a pc via crossover cable, the other to an indy with a crossover cable.

When the PC is on, I can't connect with the Indy and visa versa.

kampl · Jan 1, 2004, 10:33 PM

Originally posted by MacGorilla:
I have a cable modem plugged into the built ethernet port. I get my ip via DHCP. All this good,

In PCI slot 5 I have a d link network card. It has an ip of 192. 168.0.7

In PCI slot 4 I also have a d link ethernet card with an ip 192.168. 0.8

One card to connect to a pc via crossover cable, the other to an indy with a crossover cable.

When the PC is on, I can't connect with the Indy and visa versa.

What is the output of netstat -rn and arp -a from a terminal prompt on the Mac? Sounds like a routing problem.

kampl · Jan 1, 2004, 10:48 PM

OK, perhaps I should make a couple suggestions instead of badgering you with questions. Based on what you have said soo far, it sounds like all those interfaces are configured to be on the same segment (based on the IP addresses you have posted).

I would suggest changing the networks each interface is a member of. For instance, have one interface on the .1.0/24 one on the .2.0/24 and one on the .3.0/24 networks. Or if you have a grasp of subnetting further than class A,B,C, carve up the .0 network into smaller CIDR blocks to make each interface a member of. Following me?

MacGorilla · Jan 2, 2004, 08:33 AM

I actually don't follow you but I'm an idiot so bear with me.

Here is the netstat output:
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 24.52.172.1 UGSc 61 3874 en0
10.0.2/24 link#6 UC 4 0 en1
10.0.2.2 0:30:65:14:e2:d3 UHLW 1 54 en1 1033
10.0.2.255 ff:ff:ff:ff:ff:ff UHLWb 0 4 en1
24.52.172/23 link#4 UCS 4 0 en0
24.52.172.1 0:b:bf:16:94:4a UHLW 11 0 en0 1199
24.52.173.158 127.0.0.1 UHS 0 3 lo0
24.52.173.255 link#4 UHLWb 1 10 en0
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 23 16772 lo0
169.254 link#4 UCS 0 0 en0
192.168.0 link#5 UCS 2 0 en5
192.168.0.8 127.0.0.1 UHS 0 0 lo0
192.168.0.10 8:0:69:9:57:9e UHLW 0 5 en5 1088
192.168.0.255 link#5 UHLWb 2 27 en5
192.168.2 link#4 UC 1 0 en0
192.168.2.255 ff:ff:ff:ff:ff:ff UHLWb 0 8 en0
192.168.3 link#5 UC 3 0 en5
192.168.3.1 0:d:88:22:17:7b UHLW 0 1 lo0
192.168.3.255 ff:ff:ff:ff:ff:ff UHLWb 0 4 en5

Internet6:
Destination Gateway Flags Netif Expire
::1 ::1 UH lo0
fe80::/64 fe80::1 Uc lo0
fe80::1 link#1 UHL lo0
fe80::/64 link#4 UC en0
fe80::20a:95ff:fe68:ecbc 0:a:95:68:ec:bc UHL lo0
fe80::/64 link#5 UC en5
fe80::20d:88ff:fe22:177b 0:d:88:22:17:7b UHL lo0
fe80::/64 link#6 UC en1
fe80::230:65ff:fe04:dd5 0:30:65:4:d:d5 UHL lo0
ff01::/32 ::1 U lo0
ff02::/32 ::1 UC lo0
ff02::/32 link#4 UC en0
ff02::/32 link#5 UC en5
ff02::/32 link#6 UC en1

And here is arp:
? (10.0.2.2) at 0:30:65:14:e2:d3 on en1 [ethernet]
? (10.0.2.255) at ff:ff:ff:ff:ff:ff on en1 [ethernet]
ma-northadams2a-gate.bur.adelphia.net (24.52.172.1) at 0:b:bf:16:94:4a on en0 [ethernet]
? (24.52.173.255) at (incomplete) on en0 [ethernet]
? (192.168.0.10) at 8:0:69:9:57:9e on en5 [ethernet]
? (192.168.0.255) at (incomplete) on en5 [ethernet]
? (192.168.2.255) at ff:ff:ff:ff:ff:ff on en0 [ethernet]
? (192.168.3.1) at 0:d:88:22:17:7b on en5 permanent [ethernet]
? (192.168.3.255) at ff:ff:ff:ff:ff:ff on en5 [ethernet]

ghporter · Jan 2, 2004, 08:59 AM

You're using the Mac to share the cable modem, correct? If that's the case, you can simplify everything by buying a cable/DSL router. The router WAN port is connected directly to the cable modem, all the computers are connected to router LAN ports, and the router handles assigning IPs. The router hides the existence of anything on the LAN from the cable modem, which can be important if your ISP wants you to have only one computer connected to the modem.

Routers have another benefit: you don't have to have any specific computer running (liek your Mac) to allow another computer (say the Indie) to connect through the cable modem to the Internet. Much more flexible. Routers can be had for less than $50, and that's $50 worth of aggravation and annoyance you don't have to go through.

MacGorilla · Jan 2, 2004, 09:02 AM

I'd prefer not to but at this point I am inclined to agree. I'm going out later. If I can't figure it out by then I'll take your suggestion.