RE: networking problem? maybe
If you have more than one computer available, try linking up a switch to your second Ethernet card and running a test between two machines that should not touch the gateway. What's your internal LAN speed when the gateway is not involved? That will tell you whether it's the gateway you need to look at. To explain better: ADSL | | (a) FreeBSD GW | (b) | Switch / \ Machine 1 Machine 2 Have Machine 1 talk to Machine 2. What's your speed? If it's significantly faster, then it's time to look at the gateway. If not, look at the switch. If it's the gateway, try reconfiguring your gateway so that the (b) ethernet card talks to the ADSL line and the (a) card talks to your LAN. Any change in speed? If so, it's probably the card or the config associated with it. If not, it's probably your routing configuration. Hope this gives you something to start from! -Original Message- From: neko hime [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 06, 2004 8:02 PM To: [EMAIL PROTECTED] Subject: networking problem? maybe Hi there, i have just installed freebsd 4.9 one of my machies. This box is configured to be a gateway/router. The install was a base install, and i recompiled with the IPFILTER options. Ive added the net.inet.ip.forwarding=1 to my /etc/sysctl.conf. When accessing the internet (via ADSL/PPPoE) on the gateway machine, my downloads are very fast, and im very happy. my problem is that when i connect any computer to this LAN, the speed drops dramatically. For example: From the gateway machine speed 90K/s. From Machine attached to gateway machine speed 10K/s. Im not very good with networking, so im not exactly sure how to troubleshoot this. May someone suggest something for me to check. I would like to keep my gateway with freebsd. I hope this wasn't too confusing. thank-you aya Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem! Watchdog -- Timeout
Henrik Zagerholm wrote: Hi all! Installing 5.2 on my new box with an integraded Intel PRO 1000 CT NIC. System detects it as em0 but I cant get it to work. I'm trying dhcp and I have added the line: ifconfig_em0=DHCP in rc.conf but I still get this problem. em0: Watchdog Timeout ---Resetting IF I disable ACPI it works perfectly so I think it's IRQ related or? Please note that I am not associated with the Project while you read this. I think that this is a bug with the em driver on the 5.X series. You did note that it's a new technology release and not advertised to be suitable for everybody, right? IIRC, there have been issues with both em(4) and ACPI on the -HEAD (CURRENT, 5.X) code for a while. Good programmers are giving lots of the time and energy, coding for free to get it working, but some things are tricky. You might run without ACPI for a while, switch NICs until the problem is fixed, or run 4.9 or 4.10 [which is due out Real Soon Now(tm)] instead of 5.2 Kevin Kinsey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem! Watchdog -- Timeout
Kevin D. Kinsey, DaleCo, S.P. wrote: Henrik Zagerholm wrote: Hi all! Installing 5.2 on my new box with an integraded Intel PRO 1000 CT NIC. System detects it as em0 but I cant get it to work. I'm trying dhcp and I have added the line: ifconfig_em0=DHCP in rc.conf but I still get this problem. em0: Watchdog Timeout ---Resetting IF I disable ACPI it works perfectly so I think it's IRQ related or? Please note that I am not associated with the Project while you read this. I think that this is a bug with the em driver on the 5.X series. You did note that it's a new technology release and not advertised to be suitable for everybody, right? IIRC, there have been issues with both em(4) and ACPI on the -HEAD (CURRENT, 5.X) code for a while. Good programmers are giving lots of the time and energy, coding for free to get it working, but some things are tricky. You might run without ACPI for a while, switch NICs until the problem is fixed, or run 4.9 or 4.10 [which is due out Real Soon Now(tm)] instead of 5.2 Kevin Kinsey I guess you have a good point! =0) I just now another guy with the some NIC (Intel PRO 1000 CT) and it worked fine but it could be antoher device that is really messing up my system. What eactly do I miss with ACPI disabled? Have a good one Kevin! Sincerely, Henrik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem
Hi! I do have the same problem with my Intel Gigabit onboard NIC. The system detects it, but it doesn't work. Do you also get watchdog timeouts?? I traced it down to a PCI interrupt problem. dmesg: pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.CSAB - AE_NOT_FOUND Booting without ACPI helps!! (but breaks other stuff :( ) Cheers, Ben On Sunday 18 April 2004 22:21, Henrik Zagerholm wrote: Hi all! Installing 5.2 on my new box with an integraded Intel PRO 1000+ NIC. System detects it as em0 but I cant get it to work. I'm trying dhcp and I have added the line: ifconfig_em0=DHCP in rc.conf but I still get this problem. As far as I know there shouldnt be any problem with this NIC. My router works fine with my other bsd and win boxes... Suggestions? Take care! //Henrik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem UPDATED
On Thu, 4 Mar 2004, Steve Ireland wrote: The two interfaces are on different subnets: 192.168.0.0/24 and 192.168.10.0/24. You need to either add a static route between them or change their netmasks to at least a /21. Huh? They _must_ be on different subnets. You can't route one subnet across multiple network interfaces. Besides, a router always knows how to route packets between its own directly-attached networks, no additional routes are necessary. The problem here is that a route needs to be added for 192.168.10.0/24 - 192.168.0.100 in the upstream router(s), since the upstream router(s) do not currently know to send any packets destined for 192.168.10.0/24 to 192.168.0.100 for delivery. The upstream router is currently sending these packets to its own default gateway, which is likely even further upstream. IP routers aren't mind-readers, you have to tell them exactly where to send packets, but usually that is very simple. Running a routing protocol (such as RIP) on both the FreeBSD box in question and the upstream router(s) would automatically add the same route for you, but that is unnecessary in such a simple network configuration. -- Chris Dillon - cdillon(at)wolves.k12.mo.us FreeBSD: The fastest, most open, and most stable OS on the planet - Available for IA32, IA64, AMD64, PC98, Alpha, and UltraSPARC architectures - PowerPC, ARM, MIPS, and S/390 under development - http://www.freebsd.org Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem
On Thu, 4 Mar 2004, Kathy Quinlan wrote: I have a friend who can not get his FreeBSD 5.2 server to act as a gateway, from the internal network we can ping the external network card, but no further. From the server we can ping the entire world. I had him bring it over and set up my server (FreeBSD 4.8R as the gateway) so I now have: ISPMy Server---his Server---laptop From the laptop I can ping as far as the external nic on his server. From his server I can ping the world. I have googled, looked at the mailing list, but can not find the problem :o( I have re installed the server, incase he goofed up, same problem, I have swapped the external network card, same problem. Netstat -rn shows the default gateway (as my server) In rc.conf it has gateway_enable=YES I am out of ideas What IP addresses are used within the internal network? If you use addresses like 10., 172.16.-172.31. or 192.168.1.-191.168.254., you should use natd instead of routed on the server connected to the world outside. Regards Konrad Heuer ([EMAIL PROTECTED]) ___ ___ GWDG / __/__ ___ / _ )/ __/ _ \ Am Fassberg / _// __/ -_) -_) _ |\ \/ // / 37077 Goettingen /_/ /_/ \__/\__//___// Germany ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem UPDATED
- Original Message - From: Kathy Quinlan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, March 04, 2004 19:46 Subject: Networking problem UPDATED I have a friend who can not get his FreeBSD 5.2 server to act as a gateway, from the internal network we can ping the external network card, but no further. From the server we can ping the entire world. I had him bring it over and set up my server(FreeBSD 4.8R as the gateway) all my clients can use my FreeBSD server fine, so I do not think the problem is in it, so I now have: ISPMy Server---his Server---laptop My Server to ISP is a dynamic IP (ppp dialup) My server internal network is 192.168.0.1 His server to my server is connected to my servers hub and his server uses ip 192.168.0.100 His server to my laptop is connected with a cross over cable, his server is 192.168.10.1 My Laptop is 192.168.10.42 From the laptop I can ping as far as the external nic on his server (192.168.0.100). From his server I can ping the world. I have googled, looked at the mailing list, but can not find the problem :o( I have re installed the server, incase he goofed up, same problem, I have swapped the external network card, same problem. His Server rc.conf: defaultrouter=192.168.0.1 gateway_enable=YES hostname=osire.home.lan ifconfig_fxp0=inet 192.168.0.100 netmask 255.255.255.0 #external nic ifconfig_rl0=inet 192.168.10.1 netmask 255.255.255.0 #internal nic inetd_enable=YES saver=logo sshd_enable=YES osire# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.0.1UGS 00 fxp0 127.0.0.1 127.0.0.1 UH 0 49lo0 192.168.0 link#1 UC 00 fxp0 192.168.0.100:02:b3:99:46:d0 UHLW13 fxp0 1043 192.168.0.254 00:e0:29:9c:ea:72 UHLW0 165 fxp0 1039 192.168.10 link#2 UC 00rl0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%fxp0/64link#1UC fxp0 fe80::2a0:c9ff:fe8e:3980%fxp0 00:a0:c9:8e:39:80 UHL lo0 fe80::%rl0/64 link#2UC rl0 fe80::240:f4ff:fe3c:9deb%rl0 00:40:f4:3c:9d:eb UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#4UHL lo0 ff01::/32 ::1 U lo0 ff02::%fxp0/32link#1UC fxp0 ff02::%rl0/32 link#2UC rl0 ff02::%lo0/32 ::1 UC lo0 osire# There is no firewall or natd running on his server My Server rc.conf: Generated by Katinka 16-07-03 amd_enable=NO gateway_enable=YES hostname=webserver.kaqelectronics.dyndns.org ifconfig_fxp0=inet 192.168.0.1 netmask 255.255.255.0 ifconfig_rl0=media 10baseT/UTP up ipv6_enable=NO kern_securelevel_enable=NO portmap_enable=YES nfs_server_enable=YES mountd_flags=-r inetd_enable=YES nfs_reserved_port_only=YES saver=logo scrnmap=NO sendmail_enable=YES sshd_enable=YES tcp_extensions=YES usbd_enable=YES firewall_enable=YES firewall_type=OPEN named_enable=YES named_flags=/etc/namedb/named.conf sasl_saslauthd_enabled=YES ppp_enable=YES ppp_profile=dialup ppp_mode=ddial webserver# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default203.30.44.55 UGSc 1532442 tun0 127.0.0.1 127.0.0.1 UH 0 7361lo0 192.168.0 link#2 UC 50 fxp0 192.168.0.6link#2 UHLW1 4155 fxp0 192.168.0.10 00:e0:18:b0:53:00 UHLW2 165561 fxp0 944 192.168.0.100 00:a0:c9:8e:39:80 UHLW13 fxp0 845 192.168.0.254 00:e0:29:9c:ea:72 UHLW2 569747 fxp0 841 192.168.0.255 ff:ff:ff:ff:ff:ff UHLWb 2 2578 fxp0 203.30.44.55 202.89.160.14 UH 160 tun0 webserver# I am out of ideas Regards, Kat. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.593 / Virus Database: 376 - Release Date: 20/02/2004 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hello, The two interfaces are on different subnets: 192.168.0.0/24 and 192.168.10.0/24. You need to either add a
Re: Networking problem UPDATED - correction
That should have been /20 not /21. Sorry, Steve - Original Message - From: Kathy Quinlan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, March 04, 2004 19:46 Subject: Networking problem UPDATED I have a friend who can not get his FreeBSD 5.2 server to act as a gateway, from the internal network we can ping the external network card, but no further. From the server we can ping the entire world. I had him bring it over and set up my server(FreeBSD 4.8R as the gateway) all my clients can use my FreeBSD server fine, so I do not think the problem is in it, so I now have: ISPMy Server---his Server---laptop My Server to ISP is a dynamic IP (ppp dialup) My server internal network is 192.168.0.1 His server to my server is connected to my servers hub and his server uses ip 192.168.0.100 His server to my laptop is connected with a cross over cable, his server is 192.168.10.1 My Laptop is 192.168.10.42 From the laptop I can ping as far as the external nic on his server (192.168.0.100). From his server I can ping the world. I have googled, looked at the mailing list, but can not find the problem :o( I have re installed the server, incase he goofed up, same problem, I have swapped the external network card, same problem. His Server rc.conf: defaultrouter=192.168.0.1 gateway_enable=YES hostname=osire.home.lan ifconfig_fxp0=inet 192.168.0.100 netmask 255.255.255.0 #external nic ifconfig_rl0=inet 192.168.10.1 netmask 255.255.255.0 #internal nic inetd_enable=YES saver=logo sshd_enable=YES osire# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.0.1UGS 00 fxp0 127.0.0.1 127.0.0.1 UH 0 49lo0 192.168.0 link#1 UC 00 fxp0 192.168.0.100:02:b3:99:46:d0 UHLW13 fxp0 1043 192.168.0.254 00:e0:29:9c:ea:72 UHLW0 165 fxp0 1039 192.168.10 link#2 UC 00rl0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%fxp0/64link#1UC fxp0 fe80::2a0:c9ff:fe8e:3980%fxp0 00:a0:c9:8e:39:80 UHL lo0 fe80::%rl0/64 link#2UC rl0 fe80::240:f4ff:fe3c:9deb%rl0 00:40:f4:3c:9d:eb UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#4UHL lo0 ff01::/32 ::1 U lo0 ff02::%fxp0/32link#1UC fxp0 ff02::%rl0/32 link#2UC rl0 ff02::%lo0/32 ::1 UC lo0 osire# There is no firewall or natd running on his server My Server rc.conf: Generated by Katinka 16-07-03 amd_enable=NO gateway_enable=YES hostname=webserver.kaqelectronics.dyndns.org ifconfig_fxp0=inet 192.168.0.1 netmask 255.255.255.0 ifconfig_rl0=media 10baseT/UTP up ipv6_enable=NO kern_securelevel_enable=NO portmap_enable=YES nfs_server_enable=YES mountd_flags=-r inetd_enable=YES nfs_reserved_port_only=YES saver=logo scrnmap=NO sendmail_enable=YES sshd_enable=YES tcp_extensions=YES usbd_enable=YES firewall_enable=YES firewall_type=OPEN named_enable=YES named_flags=/etc/namedb/named.conf sasl_saslauthd_enabled=YES ppp_enable=YES ppp_profile=dialup ppp_mode=ddial webserver# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default203.30.44.55 UGSc 1532442 tun0 127.0.0.1 127.0.0.1 UH 0 7361lo0 192.168.0 link#2 UC 50 fxp0 192.168.0.6link#2 UHLW1 4155 fxp0 192.168.0.10 00:e0:18:b0:53:00 UHLW2 165561 fxp0 944 192.168.0.100 00:a0:c9:8e:39:80 UHLW13 fxp0 845 192.168.0.254 00:e0:29:9c:ea:72 UHLW2 569747 fxp0 841 192.168.0.255 ff:ff:ff:ff:ff:ff UHLWb 2 2578 fxp0 203.30.44.55 202.89.160.14 UH 160 tun0 webserver# I am out of ideas Regards, Kat. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.593 / Virus Database: 376 - Release Date: 20/02/2004 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hello, The two interfaces are on different subnets: 192.168.0.0/24 and
Re: Networking problem
On Thu, 19 Jun 2003, Tkachenko, Artem N wrote: Hi, I posted similar question some time ago but I guess I misstated the problem. I will be more careful this time. Here is my situation: Node A - LAN1 - Node B - LAN2 - Node C Why can't you just set a static route on both Node A and Node C pointing to Node B (each one using it's corresponding IP, Node A points to 129.197.244.10) and enable IP forwarding on Node B? Fer ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
