to the net with my "new" Bering router". What are you trying to do and how is it failing?
You might find it worthwhile to try some systematic ping tests to determine the scope of your problem. Can you ping (first from the router itself, then from a workatation on the LAN):
your external gateway address (66.202.48.1)
your DNS server addresses (216.47.224.66 and 216.47.224.48)
a known-good IP address on the Internet
an known-good FQN on the Internet
If any of thse fails, please describe *how * it fails (there are FAQs on the different ping responses and what they mean).
One thought ... are the workstations relying on the external DNS servers, or do you have a DNS forwarder running on the LAN (ehtier on the router or a separate workstation)? In either case, how are you telling the workstations what DNS servers to use?
Finally, if you do post diagnostics again, please read the SR FAQ first so you know which diagnostics are useful to us. You provided some of what we need to see, but not all.
At 10:25 PM 1/22/03 -0600, Jeremy A Tourville wrote:
I finally have the router NIC modules working right after changing the IO addresses to 300 and 320. Now they come up reliably every time. I think I have most of my config files set up right as well. I don't see any error messages during start up. My final hurdle it seems is getting on to the net with my "new" Bering router. My ISP has assigned me the following with a DSL Modem: Static IP 66.202.48.231 Gateway 66.202.48.1 DNS 216.47.224.66 and 216.47.224.48 My Windows 9x clients are set to obtain IP address automatically and use DHCP for WINS resoloution. I am able to successfully ping both interfaces on my Bering router. Can anyone tell me where I am going wrong? Below is the output from my router BTW I am not using port forwarding.1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:20:af:a7:0e:71 brd ff:ff:ff:ff:ff:ff inet 66.202.48.231/24 brd 66.202.48.255 scope global eth0 4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:20:af:bc:1d:d8 brd ff:ff:ff:ff:ff:ff inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1
[...]
66.202.48.0/24 dev eth0 proto kernel scope link src 66.202.48.231 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.254 default via 66.202.48.1 dev eth0
-- -------------------------------------------"Never tell me the odds!"-------- Ray Olszewski -- Han Solo Palo Alto, California, USA [EMAIL PROTECTED] ------------------------------------------------------------------------------- ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ------------------------------------------------------------------------ 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
