What the F? Calm your nerves Cappy!

Easy now, temdesign. Please re-read the LQ Rules as this sort of comment is not at all constructive. This post hsa been reported. -- J.W.

TATTLETALE.....Relax....Take a break....and Calm your damn nerves. Caluminskyboy will get it eventually.

//mod note: I strongly suggest not abusing moderators.

Hi chort (et al)

Please find below the details of the AIX and Solaris machines. These are working fine so I can't understand why the Linux box isn't working. Even know, as I've plugged the bridge into the switch, and the Linux machine into the switch, it's not on the network!

The linux machine is not contactable so I'll need to go and switch the bridge back into the NIC to get access to the machine - I won't get a chance to do that until tomorrow (it's 23:20 UK time!) so please stay with me!

Kindest regards,

Calluminsky

**********************************

hope#netstat -arn
Routing tables
Destination Gateway Flags Refs Use If PMTU Exp Groups

Route Tree for Protocol Family 2 (Internet):
default 192.168.0.15 UGc 0 0 en0 - -
127/8 127.0.0.1 U 5 192 lo0 - -
192.168.0/24 192.168.0.15 U 1 184 en0 - -
192.168.0.15 127.0.0.1 UGHS 3 33 lo0 - -

Route Tree for Protocol Family 24 (Internet v6):
::1 ::1 UH 0 0 lo0 16896 -
hope#ifconfig -a
en0: flags=e080863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT>
inet 192.168.0.15 netmask 0xffffff00 broadcast 192.168.0.255
lo0: flags=e08084b<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1/0
tcp_sendspace 65536 tcp_recvspace 65536



SunOS 5.6
pray#ifconfig -a
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
le0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.6 netmask ffffff00 broadcast 192.168.0.255
ether 8:0:20:71:bb:36
le1: flags=842<BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 0.0.0.0 netmask 0
ether 8:0:20:71:bb:36
pray#netstat -nra

Routing Table:
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
192.168.0.0 192.168.0.6 U 3 1 le0
10.0.0.0 192.168.0.1 UG 0 0
224.0.0.0 192.168.0.6 U 3 0 le0
default 192.168.0.1 UG 0 0
255.255.255.255 192.168.0.6 UHB 0 1 le0
255.255.255.255 192.168.0.6 UHB 5 0 le0
0.0.0.0 192.168.0.6 UHB 0 0 le0
0.0.0.0 192.168.0.6 UHB 5 0 le0
192.168.0.0 192.168.0.6 UHB 0 0 le0
192.168.0.0 192.168.0.6 UHB 5 0 le0
192.168.0.2 -- UHA 1 62 le0
192.168.0.6 -- UHL 0 142 le0
127.0.0.1 127.0.0.1 UH 0 4 lo0
192.168.0.255 192.168.0.6 UHB 0 2 le0
192.168.0.255 192.168.0.6 UHB 5 0 le0

That's really odd. Each of those machines is referencing the IP of it's own NIC as the gateway, rather than the IP of your DSL router. I don't have any experience with wireless bridges, so perhaps it's necessary for that reason. On your Linux box, is the gateway set to it's own IP, or to something else?

My deepest apologies. ;-)

Hi Chort (et al)

Thanks for the comments! The Linux machine has been set up to look at:

1) it's own NIC
2) the main wireless router
3) the wireless bridge

The wireless bridge does have it's own ip - I've configured it so that it's on the same range of IP addresses and the netmask is the same. That's pingable and I can reach the adsl side of things through it but only on the two Unix machines.

I tried it very briefly last night before going to bed and as soon as I disconnected the bridge from the linux machine, and cabled the Linux box into the switch, the linux machine was off the network. The NIC started flashing green/amber as if it was active but not connected to any network.

I'd normally be thinking hardware at this point but I can't see how it could be faulty since the NIC works fine directly plugged into the NIC.

Perhaps the AIX and Solaris machines use their own NIC's as gateways but routing on Linux may not like that approach and so not see the network? However since I've tried the three options above, I don't really know...

Kindest regards,

Calluminsky

Hi everyone

I had another look at the machine last night and I'm still left scratching my head.

I completely removed the network device, rebooted, then added it back in. The NIC flashed green/amber when it's plugged into the switch and I can't get out from the machine.

So then, I plugged the NIC straight into the hub and voila! The NIC is happy and green! I can ping everything on my network and once I add the wireless router as a gateway, I can get to the outside world.

I'm back at the point where I'm thinking that there must be something I've got to enable in the kernel to get it talking through a hub. The routing side of things seems to be happy and this looks like being a hardware/setup issue.

To recap, it's a linksys 10/100 NIC connected via normal cat 5 to a basic 8 port switching hub.

Any ideas would be greatly appreciated! I've gone through the usual suspects (/etc/sysconfig/network-scripts, /etc/sysconfig/network etc...)

Kindest regards,

Calluminsky

Sounds like a media mis-match. Run mii-tool when plugged into the switch, then run it when plugged into the bridge. Also, are you sure you're using a straight-through and not a crossover cable from the Linux box?

If all else fails, try playing with the speed/duplex settings on the NIC when plugged into the switch. Using mii-tool, set the speed to 100/full, 100/half, 10/full, 10/half until you get it to work. You'll need to wait several seconds after changing speeds in order for it to gain a link again.

Hi Chort

Many thanks for that - I will try when I get home or over the weekend!

I really appreciate all the help everyone has given me on this and your patience throughout!

Kindest regards,

Calluminsky

Hi everyone

Well, I'm delighted to say that the machine is now happily talking away to every other machine on the network, and it can also see both the wireless bridge and the wireless router! In fact, I'm writing this to you all now on the happily connected machine! Wahoo!

I booted the machine just now, ran mii-tool as chort suggested and voila! The green lights illuminated and that was it!

So, now I'm happy, the machine is happy, and the girlfriend is happy (no cables running around the apartment!)!!!

Thanks to everyone for their help and patience!

Kindest regards,

Calluminsky

Glad you got it working