At 03:37 PM 11/1/2003 +0000, AJ C wrote:
I have Bering 1.2 set up as a 2-interface shorewall firewall with no problems. Recently I have tried to setup a third wireless usb interface and am having a few issues:
1). On a cold boot the wireless interface (an atmel AT76C503A chipset device - modules loaded are uhci [not usb-uhic] and usbvnetr) never comes up - but on a reboot after this it comes up just fine - anyone else seen this? (The wireless.lrp package is loaded).
This suggests to me that the external device (either the wireless interface itself or a USB hub) needs more time to initialize itself than a cold-boot provides. A warm boot would not interrupt power to the external device, so it would have time to complete its initialization and be ready to respond second time around.
Just a guess, though' "never comes up" is not all that informative. What differences (if any) are reported by the modules, in your logs or the dmesg buffer,
between a cold and a warm boot?
2). I have set up the wireless interface as eth3, eth1 is connected to a local wired network and eth0 to a ADSL modem with an ethernet interface:
eth1 has an IP address of 192.168.1.254/24 and eth3 has an IP of 192.168.2.254/24. They are both configured with a zone of loc in the shorewall interfaces file, a dhcp server on the firewall is configured to give out IPs on both interfaces on their respective subnets. With a host on the wireless network I can successfully obtain an IP addrress and can ping hosts on the wired network (e.g. I can ping a host on the wired network with IP 192.168.1.1 from wireless host 192.168.2.2) however from a host on the wired network or from the firewall, I cannot ping a host on the wireless network (e.g. from 192.168.1.1 I cannot ping 192.168.2.2) and there is nothing in the shorewall log to indicate what is going on - any ideas?
This report is way to sketchy to permit real troubleshooting. Read over the SR FAQ before reposting, then tell us --
A. How the pings fail (silently, or with an error like "no route to host").
B. What the routing table on the Bering router is ("ip route show").
C. What the routing table on the LAN workstation doing the unsuccessful ping'ing shows.
One speculation: might your system be set up to NAT the WLAN to the LAN, but not the LAN to the WLAN? If so, this would (with appropriate Shorewall rules, of course) permit pings from the WLAN to the LAN, but not permit pings (or any other contact, except via port forwarding) from the LAN to the WLAN.
For anything more, I think you will need to report the details as specified in the SR FAQ (the link to it appears below).
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
