strange network problem with multiple interfaces
hi, I just installed stock FreeBSD 9.0 on a PowerEdge server with two network cards: bce0 is directly connected to isp's gateway bce1~3 are connected to the inside port of a router configured as 192.168.1.0/24 network with 192.168.1.1 as gateway If the ENTIRE content of /etc/rc.conf is: hostname=test.com ifconfig_bce0=inet 1.2.3.4 netmask 255.255.255.0 defaultrouter=1.2.3.1 #the above numbers are supplied by isp ifconfig_bce1=inet 192.168.1.4 netmask 255.255.255.0 static_routes=interface1 route_interface1=-net 192.168.1.0/24 192.168.1.1 then the machine can do all public network activities without problem, but doesn't appear to be able to connect to the router at all. In fact, if I do: tcpdmp -l -i eth1 host 192.168.1.1 and then do telnet 192.168.1.1 443, there are two wierd results: 1. the tcpdump catches nothing 2. the telnet window got the following result: Trying 192.168.1.1... telnet: connect to address 192.168.1.1: Operation not permitted telnet: Unable to connect to remote host routing table is the following: #netstat -rn DestinationGatewayFlagsRefs Use Netif Expire default1.2.3.1 UGS 0 193 bce0 1.2.3.0/24 link#1 U 00 bce0 1.2.3.4 link#1 UHS 00lo0 127.0.0.1 link#5UH 00lo0 192.168.1.0/24 192.168.1.1UGS 01 bce1 192.168.1.4 link#2 UHS 01lo0 No firewall is configured. Also unless there is a known relevant bug of the stock 9.0, we want to stick to this version for the moment due to some other concern. Could someone help to enlighten what I did wrong? Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network problem on 8.2 stable
On Fri, 18 Nov 2011, Xihong Yin wrote: I set the adapter up. Here is the output of 'dhclient em0' DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.3.1 bound to 192.168.3.41 -- renewal in 1800 seconds. 'ifconfig em0' output is em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC ether 00:26:b9:9d:30:dc inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: Ethernet autoselect (100baseTX full-duplex) status: active 'netstat -r' show there is no default route Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire 0.0.0.0link#1 U 00em0 localhost link#14UH 0 28lo0 But I can set the adapter manually by $ifconfig em0 inet 192.168.3.41/24 and it works. The question is why dhclient can't get the ip address even a lease is obtained. New to me. Does the machine have any unusual settings, like a non-default securelevel? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network problem on 8.2 stable
I set the adapter up. Here is the output of 'dhclient em0' DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.3.1 bound to 192.168.3.41 -- renewal in 1800 seconds. 'ifconfig em0' output is em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC ether 00:26:b9:9d:30:dc inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: Ethernet autoselect (100baseTX full-duplex) status: active 'netstat -r' show there is no default route Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire 0.0.0.0link#1 U 00em0 localhost link#14UH 0 28lo0 But I can set the adapter manually by $ifconfig em0 inet 192.168.3.41/24 and it works. The question is why dhclient can't get the ip address even a lease is obtained. Thanks, On Thu, 17 Nov 2011, Warren Block wrote: On Thu, 17 Nov 2011, Xihong Yin wrote: Hi, I upgraded from 8.0 stable to 8.2 stable today. Now I can't connect to the network through the network adapter. I've set DCHP and SYNCDHCP in /etc/rc.conf and it worked in 8.0. It seems the dhclient problem. The ip address can't be obtained. When I run 'dhclient em0' manually, it shows that an ip address is leased. But actually it is not. The 'ifconfig em0' always shows an address of 0.0.0.0 with active status. $dhclient em0 DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.3.1 bound to 192.168.3.39 -- renewal in 43200 seconds But $ifconfig em0 em0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC ether 6c:62:6d:03:16:31 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (10baseT/UTP half-duplex) status: active Any help would be appreciated. The interface is down: no UP in the flags. What happens if you just do it manually: ifconfig em0 up ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network problem on 8.2 stable
New to me. Does the machine have any unusual settings, like a non-default securelevel? No. There are no unusual security settings. On Fri, 18 Nov 2011, Warren Block wrote: On Fri, 18 Nov 2011, Xihong Yin wrote: I set the adapter up. Here is the output of 'dhclient em0' DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.3.1 bound to 192.168.3.41 -- renewal in 1800 seconds. 'ifconfig em0' output is em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC ether 00:26:b9:9d:30:dc inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: Ethernet autoselect (100baseTX full-duplex) status: active 'netstat -r' show there is no default route Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire 0.0.0.0link#1 U 00em0 localhost link#14UH 0 28lo0 But I can set the adapter manually by $ifconfig em0 inet 192.168.3.41/24 and it works. The question is why dhclient can't get the ip address even a lease is obtained. New to me. Does the machine have any unusual settings, like a non-default securelevel? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
network problem on 8.2 stable
Hi, I upgraded from 8.0 stable to 8.2 stable today. Now I can't connect to the network through the network adapter. I've set DCHP and SYNCDHCP in /etc/rc.conf and it worked in 8.0. It seems the dhclient problem. The ip address can't be obtained. When I run 'dhclient em0' manually, it shows that an ip address is leased. But actually it is not. The 'ifconfig em0' always shows an address of 0.0.0.0 with active status. $dhclient em0 DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.3.1 bound to 192.168.3.39 -- renewal in 43200 seconds But $ifconfig em0 em0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC ether 6c:62:6d:03:16:31 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (10baseT/UTP half-duplex) status: active Any help would be appreciated. Xihong ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network problem on 8.2 stable
On 11/17/11 17:56, Xihong Yin wrote: The ip address can't be obtained. Have you tried rebooting FreeBSD and letting it obtain the IP itself? On some OSes that has actually worked. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network problem on 8.2 stable
I did reboot. It is the same thing. On Thu, 17 Nov 2011, Edward Martinez wrote: On 11/17/11 17:56, Xihong Yin wrote: The ip address can't be obtained. Have you tried rebooting FreeBSD and letting it obtain the IP itself? On some OSes that has actually worked. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network problem on 8.2 stable
On 11/17/11 18:41, Xihong Yin wrote: I did reboot. It is the same thing. On Thu, 17 Nov 2011, Edward Martinez wrote: On 11/17/11 17:56, Xihong Yin wrote: The ip address can't be obtained. Have you tried rebooting FreeBSD and letting it obtain the IP itself? On some OSes that has actually worked. Did you try configure the nic with sysinstall? I think FreeBSD 8.2 has a updated em driver. You may need to download the newest FreeBSD em driver from intel. http://downloadcenter.intel.com/Detail_Desc.aspx?agr=YDwnldID=17509keyword=%22em%22DownloadType=DriversOSFullname=FreeBSD*lang=eng ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network problem on 8.2 stable
I think the driver that comes with 8.2 stable just works fine. When I manually run dhclient em0, it says ip address obtained. but ifconfig em0 shows ip address of 0.0.0.0. And there is no default route in the 'netstat -r' output. On Thu, 17 Nov 2011, Edward Martinez wrote: On 11/17/11 18:41, Xihong Yin wrote: I did reboot. It is the same thing. On Thu, 17 Nov 2011, Edward Martinez wrote: On 11/17/11 17:56, Xihong Yin wrote: The ip address can't be obtained. Have you tried rebooting FreeBSD and letting it obtain the IP itself? On some OSes that has actually worked. Did you try configure the nic with sysinstall? I think FreeBSD 8.2 has a updated em driver. You may need to download the newest FreeBSD em driver from intel. http://downloadcenter.intel.com/Detail_Desc.aspx?agr=YDwnldID=17509keyword=%22em%22DownloadType=DriversOSFullname=FreeBSD*lang=eng ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network problem on 8.2 stable
On Thu, 17 Nov 2011, Xihong Yin wrote: Hi, I upgraded from 8.0 stable to 8.2 stable today. Now I can't connect to the network through the network adapter. I've set DCHP and SYNCDHCP in /etc/rc.conf and it worked in 8.0. It seems the dhclient problem. The ip address can't be obtained. When I run 'dhclient em0' manually, it shows that an ip address is leased. But actually it is not. The 'ifconfig em0' always shows an address of 0.0.0.0 with active status. $dhclient em0 DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.3.1 bound to 192.168.3.39 -- renewal in 43200 seconds But $ifconfig em0 em0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC ether 6c:62:6d:03:16:31 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (10baseT/UTP half-duplex) status: active Any help would be appreciated. The interface is down: no UP in the flags. What happens if you just do it manually: ifconfig em0 up ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: KVM - FreeBSD Network Problem
On 10/07/11 01:01, Aydın Demirel wrote: Hi; I installed FreeBSD 8.2 on Centos 5.7 via KVM. KVM version is 8.3 and qemu version is 0.12.4 We have network problem. I set guest freebsd network as bridge mode and Status seems active. Default gateway is defined.. When I see network packets with tcpdump, packets are streaming (for example: ARP, requested has 10.6.21.221 ...) But, Guest network doesn't go out. What can be the problem? Any suggestion? Regards I have noticed odd behaviour when using Gentoo as the KVM host. I get very intermitant connectivity. I have it setup as a bridge on the host. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
KVM - FreeBSD Network Problem
Hi; I installed FreeBSD 8.2 on Centos 5.7 via KVM. KVM version is 8.3 and qemu version is 0.12.4 We have network problem. I set guest freebsd network as bridge mode and Status seems active. Default gateway is defined.. When I see network packets with tcpdump, packets are streaming (for example: ARP, requested has 10.6.21.221 ...) But, Guest network doesn't go out. What can be the problem? Any suggestion? Regards -- *Aydın Demirel Endersys Ltd. Sistem Destek Mühendisi/ System Support Engineer* * *Endersys is the first Advanced Business Partner of Red Hat in Turkey! http://www.europe.redhat.com/partners/endersys/ Phone : +90 216 470 9423 | GSM : +90 530 401 8203 Fax : +90 216 470 9508 | Web : http://www.endersys.com http://www.endersys.com/ Blog : http://blog.endersys.com http://blog.endersys.com/ Twitter : http://www.twitter.com/endersys LPI : The #1 Linux Certification for IT Professionals LPI (Linux Professional Institute) Turkey http://www.lpi-turkey.com http://www.lpi-turkey.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: KVM - FreeBSD Network Problem
What can be the problem? Any suggestion? Show us: ifconfig -a arp -an netstat -rn netstat -i netstat -s Are other KVM guests on this hypervisor working? Are you briding or routing/NAT from your hypervisor? ~BAS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Can't fetch portsnap because of network problem
Hi, I'm trying to fetch portsnap but can't because probably of network problem. Whenever I try to run command # portsnap fetch extract the process stall and never reach 20%. It is sad. :( The computer on wich I try to run this command is on my home LAN that has a gateway/router. What can I do to solve this problem? -- Best Regards, Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't fetch portsnap because of network problem
On 03/04/2011 14:45, Paul Chany wrote: I'm trying to fetch portsnap but can't because probably of network problem. Whenever I try to run command # portsnap fetch extract the process stall and never reach 20%. It is sad. :( The computer on wich I try to run this command is on my home LAN that has a gateway/router. What can I do to solve this problem? You need to diagnose why your fetch is bombing out. Start by checking over your own equipment and try to eliminate that as a source of problems. Make sure all your cabling is in good condition and that all network plugs are correctly seated. Check for packet errors: # netstat -i Anything non-zero in the Ierrs or Oerrs columns is a cause for concern, especially if the error counters are going up over time. If your gateway/router has the capability, check for the same sort of errors there. Having eliminated your own kit as a source of problems, try looking for network problems between the portsnap servers and you. mtr(8) is good for this purpose, but (of course) catch22: to install it, you'ld need a working ports tree... mtr will show up packet loss on intermediate network links, and various sorts of routing problems. If these are present, then you need to contact your ISP who should be able to sort things out on your behalf. Finally, one thing that can screw up portsnap is a poorly implemented transparent HTTP proxy. My advice: *don't use ISPs that force you to use transparent proxying*. However, if this is what you are lumbered with, then there is a simple work-around: use csup(1) instead of portsnap(8). csup doesn't run over HTTP, so it can't be mangled by broken proxies. Now, if you need help with any of this, you can certainly post here, but for best results you'll need to supply a lot more detail about exactly what it was you did and exactly what the result was. Cut'n'paste from the terminal is good, or use script(1) to save a transcript of a terminal session. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Can't fetch portsnap because of network problem
2011-04-03 16:19 keltezéssel, Matthew Seaman írta: On 03/04/2011 14:45, Paul Chany wrote: I'm trying to fetch portsnap but can't because probably of network problem. Whenever I try to run command # portsnap fetch extract the process stall and never reach 20%. It is sad. :( The computer on wich I try to run this command is on my home LAN that has a gateway/router. What can I do to solve this problem? You need to diagnose why your fetch is bombing out. Start by checking over your own equipment and try to eliminate that as a source of problems. Make sure all your cabling is in good condition and that all network plugs are correctly seated. Check for packet errors: # netstat -i All my cabling is in good condition and all network plugs are correctly seated. I attached the output of '# netstat -i' command in netstat.log file. One can see there are 26 Oerrs in the file. Informations of my home LAN are: domain: excito gateway: 192.168.10.1 name server: 192.168.10.1 netmask: 255.255.255.0 Any advices will be appreciated! -- Best Regards, Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't fetch portsnap because of network problem
2011-04-03 18:35 keltezéssel, Paul Chany írta: 2011-04-03 16:19 keltezéssel, Matthew Seaman írta: On 03/04/2011 14:45, Paul Chany wrote: I'm trying to fetch portsnap but can't because probably of network problem. Whenever I try to run command # portsnap fetch extract the process stall and never reach 20%. It is sad. :( The computer on wich I try to run this command is on my home LAN that has a gateway/router. What can I do to solve this problem? You need to diagnose why your fetch is bombing out. Start by checking over your own equipment and try to eliminate that as a source of problems. Make sure all your cabling is in good condition and that all network plugs are correctly seated. Check for packet errors: # netstat -i All my cabling is in good condition and all network plugs are correctly seated. I attached the output of '# netstat -i' command in netstat.log file. Well, it seems that one can't to send mail with attached file onto list, right? Here is the output of netstat -i: NameMtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll plip0 1500 Link#1 0 0 0 0 0 0 lo0 16384 Link#2 0 0 0 0 0 0 lo0 16384 fe80:2::1 fe80:2::10 - - 0 - - lo0 16384 localhost ::1 0 - - 0 - - lo0 16384 your-net localhost0 - - 0 - - ue01500 Link#3 00:00:e8:00:11:f172968 0 0 4867126 0 ue01500 192.168.10.0 cspetoile.localdo72934 - - 48682 - - -- Best Regards, Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't fetch portsnap because of network problem
2011-04-03 16:19 keltezéssel, Matthew Seaman írta: On 03/04/2011 14:45, Paul Chany wrote: I'm trying to fetch portsnap but can't because probably of network problem. Whenever I try to run command # portsnap fetch extract the process stall and never reach 20%. It is sad. :( The computer on wich I try to run this command is on my home LAN that has a gateway/router. What can I do to solve this problem? You need to diagnose why your fetch is bombing out. Start by checking over your own equipment and try to eliminate that as a source of problems. Make sure all your cabling is in good condition and that all network plugs are correctly seated. Check for packet errors: # netstat -i Anything non-zero in the Ierrs or Oerrs columns is a cause for concern, especially if the error counters are going up over time. If your gateway/router has the capability, check for the same sort of errors there. On my gateway/router the output of 'netstat -i' command is_ Kernel Interface table Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg eth0 1500 0 7914770 0 0 0 3427615 0 0 0 BRU eth1 1500 0 3369182 0 0 0 5234370 0 0 0 ABMRU lo16436 0 1193 0 0 0 1193 0 0 0 LRU -- Best Regards, Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't fetch portsnap because of network problem
2011-04-03 16:19 keltezéssel, Matthew Seaman írta: On 03/04/2011 14:45, Paul Chany wrote: I'm trying to fetch portsnap but can't because probably of network problem. Whenever I try to run command # portsnap fetch extract the process stall and never reach 20%. It is sad. :( The computer on wich I try to run this command is on my home LAN that has a gateway/router. What can I do to solve this problem? You need to diagnose why your fetch is bombing out. Start by checking over your own equipment and try to eliminate that as a source of problems. Make sure all your cabling is in good condition and that all network plugs are correctly seated. Check for packet errors: # netstat -i Well, maybe this does not cause the solution but: I change in /etc/portsnap.conf the server from: SERVERNAME=portsnap.FreeBSD.org to a portsnap mirror: SERVERNAME=portsnap1.FreeBSD.org and after that I can fetch ports. -- Best Regards, Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: u3g network problem
On Wed, Mar 31, 2010 at 1:12 PM, Patrick Lamaiziere patf...@davenulle.org wrote: Le Wed, 31 Mar 2010 08:18:26 -0400, Alejandro Imass a...@p2ee.org a écrit : On Tue, Mar 30, 2010 at 5:27 PM, Patrick Lamaiziere patf...@davenulle.org wrote: [...] I use ppp (wvdial does not seem ported to FreeBSD, is it a Linux only program?) I only dial out with my laptop which has Debian on it, and I assumed that there was a FBSD port. Sorry, about that. I guess you're right, but it seems odd that it's not ported to FBSD being such a friendly tool for ppp. I found the sources here: http://alumnit.ca/wiki/?WvDial but the wvstreams library does not compile right off the bat. Sadly I don't have the time/need to play with this but if I did I would definitively try to get it to run on FBSD if it were possible. Best, Alejandro Imass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: u3g network problem
On Tue, Mar 30, 2010 at 5:27 PM, Patrick Lamaiziere patf...@davenulle.org wrote: (8-STABLE/i386) Hi, I've got some troubles with a 3G connection. I don't know which things I should check to debug this: I use ppp to connect and it works fine. But after a while (not a long time), I don't have any reply to DNS requests, as far I can see with wireshark... What are you using to dial to your 3g network? (I use wvdial, and love it) I've seen this happen on my 3g network as well. It seems that the ISP randomly updates the DNS to a broken one. So write down the DNSs when it's actually working (cat /etc/resolv.conf) and make yourself a little script that updates them back to the working DNSs here is mine for example (adjust to your working DNSs): # cat ./dnsdigitel #!/bin/sh echo nameserver 204.59.152.208 /etc/resolv.conf echo nameserver 57.73.127.195 /etc/resolv.conf So when it stops resolving I just ./dnsdigitel and that's it. Of course, this could be easily automated, etc. but it's a quick fix to your problem. Now, the interesting this is that your ISP does exactly the same as my ISP, it changes the DNS randomly to non-working ones, curious. Best, Alejandro Imass Then if I use an IP, it works. So it looks like it is a problem with DNS. I've tried with an other dns server with the same result. I've also tried with a local dns server to cache the requests. It looks to help a bit. Anyway I also use a ssh tunnel to connect to my server and (on the server) I can see a lot of CLOSED sockets with netstat, and a lot of sshd processes stuck, even after days. So there is something wrong with the connection. Any idea or suggestion? Thanks, regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: u3g network problem
Le Wed, 31 Mar 2010 08:18:26 -0400, Alejandro Imass a...@p2ee.org a écrit : On Tue, Mar 30, 2010 at 5:27 PM, Patrick Lamaiziere patf...@davenulle.org wrote: I've got some troubles with a 3G connection. I don't know which things I should check to debug this: I use ppp to connect and it works fine. But after a while (not a long time), I don't have any reply to DNS requests, as far I can see with wireshark... What are you using to dial to your 3g network? (I use wvdial, and love it) I use ppp (wvdial does not seem ported to FreeBSD, is it a Linux only program?) I've seen this happen on my 3g network as well. It seems that the ISP randomly updates the DNS to a broken one. So write down the DNSs when it's actually working (cat /etc/resolv.conf) and make yourself a little script that updates them back to the working DNSs here is mine for example (adjust to your working DNSs): I don't think that is the problem, I've already tried this (use opendns). Thanks for the idea however. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: u3g network problem
Hi, If your DNS are changed, I think that your network card is configured in DHCP mode. To dissallow DNS changes (in /etc/resolv.conf) by DHCP updates, you can add this line to /etc/dhclient.conf : prepend domain-name-servers DNS_IP_adress_1,DNS_IP_adresse_2,DNS_IP_adresse_3; After you must restart your network card and voilà. Alexandre. --- En date de : Mer 31.3.10, Alejandro Imass a...@p2ee.org a écrit : De: Alejandro Imass a...@p2ee.org Objet: Re: u3g network problem À: Patrick Lamaiziere patf...@davenulle.org Cc: freebsd-questions@freebsd.org Date: Mercredi 31 mars 2010, 12h18 On Tue, Mar 30, 2010 at 5:27 PM, Patrick Lamaiziere patf...@davenulle.org wrote: (8-STABLE/i386) Hi, I've got some troubles with a 3G connection. I don't know which things I should check to debug this: I use ppp to connect and it works fine. But after a while (not a long time), I don't have any reply to DNS requests, as far I can see with wireshark... What are you using to dial to your 3g network? (I use wvdial, and love it) I've seen this happen on my 3g network as well. It seems that the ISP randomly updates the DNS to a broken one. So write down the DNSs when it's actually working (cat /etc/resolv.conf) and make yourself a little script that updates them back to the working DNSs here is mine for example (adjust to your working DNSs): # cat ./dnsdigitel #!/bin/sh echo nameserver 204.59.152.208 /etc/resolv.conf echo nameserver 57.73.127.195 /etc/resolv.conf So when it stops resolving I just ./dnsdigitel and that's it. Of course, this could be easily automated, etc. but it's a quick fix to your problem. Now, the interesting this is that your ISP does exactly the same as my ISP, it changes the DNS randomly to non-working ones, curious. Best, Alejandro Imass Then if I use an IP, it works. So it looks like it is a problem with DNS. I've tried with an other dns server with the same result. I've also tried with a local dns server to cache the requests. It looks to help a bit. Anyway I also use a ssh tunnel to connect to my server and (on the server) I can see a lot of CLOSED sockets with netstat, and a lot of sshd processes stuck, even after days. So there is something wrong with the connection. Any idea or suggestion? Thanks, regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: u3g network problem
If your DNS are changed, I think that your network card is configured in DHCP mode. To dissallow DNS changes (in /etc/resolv.conf) by DHCP updates, you can add this line to /etc/dhclient.conf : prepend domain-name-servers DNS_IP_adress_1,DNS_IP_adresse_2,DNS_IP_adresse_3; After you must restart your network card and voilà. Better if you write supersede domain-name-servers IP instead. Regards Alberto Mijares ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
u3g network problem
(8-STABLE/i386) Hi, I've got some troubles with a 3G connection. I don't know which things I should check to debug this: I use ppp to connect and it works fine. But after a while (not a long time), I don't have any reply to DNS requests, as far I can see with wireshark... Then if I use an IP, it works. So it looks like it is a problem with DNS. I've tried with an other dns server with the same result. I've also tried with a local dns server to cache the requests. It looks to help a bit. Anyway I also use a ssh tunnel to connect to my server and (on the server) I can see a lot of CLOSED sockets with netstat, and a lot of sshd processes stuck, even after days. So there is something wrong with the connection. Any idea or suggestion? Thanks, regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network problem
A large number of ISPs block port 80 requests and do not inform you. With Verizon, you need to redirect external http requests to a different port that is not blocked or pay for the business connection. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
network problem
After a recent change of ISP and hence our external IP address I find that our FreeBSD 6.1 apache http server appears to be invisible from outside our site. Port 80 requests just seem to hang whether done via a dns lookup or using the ip address. Checking the logs seems to indicate that no requests now arrive, but that we have seen some external requests since the ISP changed. The https/sshd/mysql etc servers are still visible externally and the http server is visible on its local address and if you visit the external address from inside the network. I suspect that either I've still got some misconfiguration on the server, gateway or or dns(although this seems less likely). Alternatively the ISP might have some other block in place. I've looked for the old IP address in /etc and found no usages the gateway appears to be correctly set up. What tests can I do internally/externally to see what happens to my port 80 packets? -- Robin Becker ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: network problem
whats redirecting the requests to the apache server? is it on piublic or private ip block ? whats it set to listen on IP wise ? what about a changed netmask ? On Saturday 16 August 2008 15:55:11 Robin Becker wrote: After a recent change of ISP and hence our external IP address I find that our FreeBSD 6.1 apache http server appears to be invisible from outside our site. Port 80 requests just seem to hang whether done via a dns lookup or using the ip address. Checking the logs seems to indicate that no requests now arrive, but that we have seen some external requests since the ISP changed. The https/sshd/mysql etc servers are still visible externally and the http server is visible on its local address and if you visit the external address from inside the network. I suspect that either I've still got some misconfiguration on the server, gateway or or dns(although this seems less likely). Alternatively the ISP might have some other block in place. I've looked for the old IP address in /etc and found no usages the gateway appears to be correctly set up. What tests can I do internally/externally to see what happens to my port 80 packets? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: network problem
OutBackDingo wrote: whats redirecting the requests to the apache server? is it on piublic or private ip block ? whats it set to listen on IP wise ? what about a changed netmask ? The server is listening to a local ip address which hasn't changed eg 192.168.0.x The external IP address was changed as was the external name server and the netmask. Our local net is provided by an ethernet router that has been configured with the new external IP address in exactly the same way as the old one. I've just reviewed the settings again and both https(443) and http(80) appear to be NAT'd to 192.168.0.x which is both the http https server. Https works http doesn't. The external IP is xxx.yyy.zzz.240 with netmask xxx.yyy.zzz.224 and gateway xxx.yyy.zzz.225 and I think that works. The dns server ip is setup in the gateway and it acts as both a dhcp server and static router. When I connect from the lan side to http://xxx.yyy.zzz.240 it seems to work fine. From outside it fails. On Saturday 16 August 2008 15:55:11 Robin Becker wrote: After a recent change of ISP and hence our external IP address I find that our FreeBSD 6.1 apache http server appears to be invisible from outside our site. Port 80 requests just seem to hang whether done via a dns lookup or using the ip address. Checking the logs seems to indicate that no requests now arrive, but that we have seen some external requests since the ISP changed. The https/sshd/mysql etc servers are still visible externally and the http server is visible on its local address and if you visit the external address from inside the network. I suspect that either I've still got some misconfiguration on the server, gateway or or dns(although this seems less likely). Alternatively the ISP might have some other block in place. I've looked for the old IP address in /etc and found no usages the gateway appears to be correctly set up. What tests can I do internally/externally to see what happens to my port 80 packets? ... -- Robin Becker ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: network problem
Double check your network configuration. Double check your firewall configuration. Try to telnet the ip address from the outside on port 80. Try to nmap from the outside the ip address and see what is the result. -- paolo The external IP address was changed as was the external name server and the netmask. Our local net is provided by an ethernet router that has been configured with the new external IP address in exactly the same way as the old one. I've just reviewed the settings again and both https(443) and http(80) appear to be NAT'd to 192.168.0.x which is both the http https server. Https works http doesn't. The external IP is xxx.yyy.zzz.240 with netmask xxx.yyy.zzz.224 and gateway xxx.yyy.zzz.225 and I think that works. The dns server ip is setup in the gateway and it acts as both a dhcp server and static router. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Weird network problem
I just installed 7.0 STABLE on a brand new Dell SC1435 (dual AMD 64bit dual core processors), and I'm experiencing a very weird problem. If I try to do anything with the network, I lose connectivy. For example, if I run /etc/rc.d/netif restart, when the interface comes back up, it says the media has no connection. If I reboot the box, it works fine. If I try to bring up an alias interface on the same NIC the network goes away and the box has to be rebooted. Did something change on 7.0? Or have I got some sort of bug? [EMAIL PROTECTED] ~]$ uname -a FreeBSD www.stovebolt.com 7.0-STABLE FreeBSD 7.0-STABLE #0: Fri Jun 27 23:01:26 CDT 2008 root@:/usr/obj/usr/src/sys/GENERIC amd64 [EMAIL PROTECTED] ~]$ grep bge /var/run/dmesg.boot bge0: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4201 mem 0xefcf-0xefcf irq 33 at device 0.0 on pci1 miibus0: MII bus on bge0 bge0: Ethernet address: 00:1e:c9:46:1c:a0 bge0: [ITHREAD] bge1: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4201 mem 0xefdf-0xefdf irq 37 at device 0.0 on pci2 miibus1: MII bus on bge1 bge1: Ethernet address: 00:1e:c9:46:1c:a1 bge1: [ITHREAD] Paul Schmehl As if it wasn't already obvious, my opinions are my own and not those of my employer.
FreeBSD network problem.
I have such a strange problem I cant even guess whats worng. Im running FreeBSD 7.0-RELEASE amd64 and zfs. When the machine starts everything works fine but after a while (the only thing I noticed, when the free memory drops below 1700MB) it starts to behave VERY strange when serving web-pages (running apache22). It has no problem serving html-pages but css and images doesnt work. The http-log reports 200 OK and tcpdump shows the whole css-code sent out on the interface. But the browser/telnet just sits there waiting for data. Sometimes we even get HTTP-requests inside the css-file from another machine to another server. (see picture) http://jf.jail.se/tmp/css.png When I reboot the machine everything works fine again but after a while this appears again. using lynx is no problem at all. or telnet and GET / HTTP/1.1 Host: blabla this gives the correct data, but GET /style.css HTTP/1.1 gives nothing, just waiting for data. Other protocols like ftp, ssh, smtp, imap seems to work fine. And sometimes it seems like it works fine UNTIL you do shift+reload until that the sites works fine. of course I figured that this must be a problem between the server and myself but since a reboot fixes the problem for a certain amout of time that could (maybe) not be the case. I really need some ideas on this.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Problem in FreeBSD 6.2-RELEASE-p5
Please don't top-post; I had to delete the earlier comments from this message because it had become impossible to follow. When you hit the connection limit, does anything appear in the logs? -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Problem in FreeBSD 6.2-RELEASE-p5
ammm I don't have checked any log files.. just test with my portscan program.. and too when I have blocked when used BitCommet.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Problem in FreeBSD 6.2-RELEASE-p5
Please don't top-post. ExTaZyTi [EMAIL PROTECTED] writes: Is the FreeBSD machine performing NAT for the Windows box? extazyti: yes with PF firewall. (But I don't have this problem before re-build my world+kernel (my last fbsd was fbsd6.2-STABLE. But this problem exist again in fbsd6.2-STABLE when I have build option ot drop TCP+SYN and have some bug..I donk know what exactly)) Are you saying that this is a second problem? extazyti: YES. because I think limmiting my connectins is normal when I have net.inet.tcp.blackhole=2 but Now I haven't this sysctl option and this is problem again. How are you doing the scan, and how do you know the ports are not really open? extazyti: I use PortScan with a delay MS - 20 (He sends TCP4-sockets) and ports It's not really open because there is no program to open random ports with this values and I use the netstat command. Aslo this problem was again before time when I have bugged again my kernel with TCP_DROP SYN+FIN in my kernel. netstat isn't the best way to figure this out. It can be confusing. Try sockstat(1). Which sysctl? extazyti: ALL, I put # before all texts in my sysctl.conf and reboot my system. Check them after the reboot, using the sysctl(8) command and the particular sysctl. Are you sure that the sysctl value changed? extazyti: I think yes..after restart and I changed special net.inet.tcp.blackhole to 0. So check it: $ sysctl net.inet.tcp.blackhole net.inet.tcp.blackhole: 0 $ Did you look at it after changing it to make sure it really shows up as different? extazyti: No. But I think reboot changes to default this options when have # before all texts in /etc/sysctl.conf If nothing else affects it, yes. But check to be sure. 2007/6/22, Lowell Gilbert [EMAIL PROTECTED]: [lists trimmed to just -questions] ExTaZyTi [EMAIL PROTECTED] writes: I have a serious problem with my network. I have connected 2 PC's, 1 - FreeBSD, 2 - Windows XP. The problem is follow - My FreeBSD limmiting connections , I cannot open more 224 TCP4-Sockets in my Windows Box. When I downloading torrent file, I cannot create more connections to the web, and while this time I can't open for example - web sites. Is the FreeBSD machine performing NAT for the Windows box? Tow problem who worry myself is when I scan a my freebsd box or other server for open ports its FAKE show me: 81 82 ,83 ,465,463 and other ports open.. but It's FAKE .. it's not really open.. Are you saying that this is a second problem? How are you doing the scan, and how do you know the ports are not really open? I Cleared my sysctl, and test, cleared my firewall and test, re-build my kernel with any options changed and test again.. Just don't Work :(( Which sysctl? I have use PF firewall and FreeBSD 6.2-RELEASE-p5. I Think this problem is from net.inet.tcp.blackhole=2 in my sysctl because it's work before i do sysctl -w net.inet.tcp.blackhole=2.. but when back this option to value = 0 this problem is stay there.. and no restarts or re-build my kernel can fix this..or maybe be wrong to this supposition. Sorry for my english. Are you sure that the sysctl value changed? Did you look at it after changing it to make sure it really shows up as different? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Problem in FreeBSD 6.2-RELEASE-p5
I've already checket with sockstat. Yes net.inet.tcp.blackhole: 0 this is my net.inet.tcp.blackhole value 0.. I don't know how ti fix this.. I try to migrate to FreeBSD 5.5 but when build the kernel of fbsd-5.5 I have some errors and back again to the 6.2...backup kernel.. 2007/6/24, Lowell Gilbert [EMAIL PROTECTED]: Please don't top-post. ExTaZyTi [EMAIL PROTECTED] writes: Is the FreeBSD machine performing NAT for the Windows box? extazyti: yes with PF firewall. (But I don't have this problem before re-build my world+kernel (my last fbsd was fbsd6.2-STABLE. But this problem exist again in fbsd6.2-STABLE when I have build option ot drop TCP+SYN and have some bug..I donk know what exactly)) Are you saying that this is a second problem? extazyti: YES. because I think limmiting my connectins is normal when I have net.inet.tcp.blackhole=2 but Now I haven't this sysctl option and this is problem again. How are you doing the scan, and how do you know the ports are not really open? extazyti: I use PortScan with a delay MS - 20 (He sends TCP4-sockets) and ports It's not really open because there is no program to open random ports with this values and I use the netstat command. Aslo this problem was again before time when I have bugged again my kernel with TCP_DROP SYN+FIN in my kernel. netstat isn't the best way to figure this out. It can be confusing. Try sockstat(1). Which sysctl? extazyti: ALL, I put # before all texts in my sysctl.conf and reboot my system. Check them after the reboot, using the sysctl(8) command and the particular sysctl. Are you sure that the sysctl value changed? extazyti: I think yes..after restart and I changed special net.inet.tcp.blackhole to 0. So check it: $ sysctl net.inet.tcp.blackhole net.inet.tcp.blackhole: 0 $ Did you look at it after changing it to make sure it really shows up as different? extazyti: No. But I think reboot changes to default this options when have # before all texts in /etc/sysctl.conf If nothing else affects it, yes. But check to be sure. 2007/6/22, Lowell Gilbert [EMAIL PROTECTED]: [lists trimmed to just -questions] ExTaZyTi [EMAIL PROTECTED] writes: I have a serious problem with my network. I have connected 2 PC's, 1 - FreeBSD, 2 - Windows XP. The problem is follow - My FreeBSD limmiting connections , I cannot open more 224 TCP4-Sockets in my Windows Box. When I downloading torrent file, I cannot create more connections to the web, and while this time I can't open for example - web sites. Is the FreeBSD machine performing NAT for the Windows box? Tow problem who worry myself is when I scan a my freebsd box or other server for open ports its FAKE show me: 81 82 ,83 ,465,463 and other ports open.. but It's FAKE .. it's not really open.. Are you saying that this is a second problem? How are you doing the scan, and how do you know the ports are not really open? I Cleared my sysctl, and test, cleared my firewall and test, re-build my kernel with any options changed and test again.. Just don't Work :(( Which sysctl? I have use PF firewall and FreeBSD 6.2-RELEASE-p5. I Think this problem is from net.inet.tcp.blackhole=2 in my sysctl because it's work before i do sysctl -w net.inet.tcp.blackhole=2.. but when back this option to value = 0 this problem is stay there.. and no restarts or re-build my kernel can fix this..or maybe be wrong to this supposition. Sorry for my english. Are you sure that the sysctl value changed? Did you look at it after changing it to make sure it really shows up as different? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Problem in FreeBSD 6.2-RELEASE-p5
[lists trimmed to just -questions] ExTaZyTi [EMAIL PROTECTED] writes: I have a serious problem with my network. I have connected 2 PC's, 1 - FreeBSD, 2 - Windows XP. The problem is follow - My FreeBSD limmiting connections , I cannot open more 224 TCP4-Sockets in my Windows Box. When I downloading torrent file, I cannot create more connections to the web, and while this time I can't open for example - web sites. Is the FreeBSD machine performing NAT for the Windows box? Tow problem who worry myself is when I scan a my freebsd box or other server for open ports its FAKE show me: 81 82 ,83 ,465,463 and other ports open.. but It's FAKE .. it's not really open.. Are you saying that this is a second problem? How are you doing the scan, and how do you know the ports are not really open? I Cleared my sysctl, and test, cleared my firewall and test, re-build my kernel with any options changed and test again.. Just don't Work :(( Which sysctl? I have use PF firewall and FreeBSD 6.2-RELEASE-p5. I Think this problem is from net.inet.tcp.blackhole=2 in my sysctl because it's work before i do sysctl -w net.inet.tcp.blackhole=2.. but when back this option to value = 0 this problem is stay there.. and no restarts or re-build my kernel can fix this..or maybe be wrong to this supposition. Sorry for my english. Are you sure that the sysctl value changed? Did you look at it after changing it to make sure it really shows up as different? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Problem in FreeBSD 6.2-RELEASE-p5
Is the FreeBSD machine performing NAT for the Windows box? extazyti: yes with PF firewall. (But I don't have this problem before re-build my world+kernel (my last fbsd was fbsd6.2-STABLE. But this problem exist again in fbsd6.2-STABLE when I have build option ot drop TCP+SYN and have some bug..I donk know what exactly)) Are you saying that this is a second problem? extazyti: YES. because I think limmiting my connectins is normal when I have net.inet.tcp.blackhole=2 but Now I haven't this sysctl option and this is problem again. How are you doing the scan, and how do you know the ports are not really open? extazyti: I use PortScan with a delay MS - 20 (He sends TCP4-sockets) and ports It's not really open because there is no program to open random ports with this values and I use the netstat command. Aslo this problem was again before time when I have bugged again my kernel with TCP_DROP SYN+FIN in my kernel. Which sysctl? extazyti: ALL, I put # before all texts in my sysctl.conf and reboot my system. Are you sure that the sysctl value changed? extazyti: I think yes..after restart and I changed special net.inet.tcp.blackhole to 0. Did you look at it after changing it to make sure it really shows up as different? extazyti: No. But I think reboot changes to default this options when have # before all texts in /etc/sysctl.conf 2007/6/22, Lowell Gilbert [EMAIL PROTECTED]: [lists trimmed to just -questions] ExTaZyTi [EMAIL PROTECTED] writes: I have a serious problem with my network. I have connected 2 PC's, 1 - FreeBSD, 2 - Windows XP. The problem is follow - My FreeBSD limmiting connections , I cannot open more 224 TCP4-Sockets in my Windows Box. When I downloading torrent file, I cannot create more connections to the web, and while this time I can't open for example - web sites. Is the FreeBSD machine performing NAT for the Windows box? Tow problem who worry myself is when I scan a my freebsd box or other server for open ports its FAKE show me: 81 82 ,83 ,465,463 and other ports open.. but It's FAKE .. it's not really open.. Are you saying that this is a second problem? How are you doing the scan, and how do you know the ports are not really open? I Cleared my sysctl, and test, cleared my firewall and test, re-build my kernel with any options changed and test again.. Just don't Work :(( Which sysctl? I have use PF firewall and FreeBSD 6.2-RELEASE-p5. I Think this problem is from net.inet.tcp.blackhole=2 in my sysctl because it's work before i do sysctl -w net.inet.tcp.blackhole=2.. but when back this option to value = 0 this problem is stay there.. and no restarts or re-build my kernel can fix this..or maybe be wrong to this supposition. Sorry for my english. Are you sure that the sysctl value changed? Did you look at it after changing it to make sure it really shows up as different? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Network Problem in FreeBSD 6.2-RELEASE-p5
Hi, I have a serious problem with my network. I have connected 2 PC's, 1 - FreeBSD, 2 - Windows XP. The problem is follow - My FreeBSD limmiting connections , I cannot open more 224 TCP4-Sockets in my Windows Box. When I downloading torrent file, I cannot create more connections to the web, and while this time I can't open for example - web sites. Tow problem who worry myself is when I scan a my freebsd box or other server for open ports its FAKE show me: 81 82 ,83 ,465,463 and other ports open.. but It's FAKE .. it's not really open.. I Cleared my sysctl, and test, cleared my firewall and test, re-build my kernel with any options changed and test again.. Just don't Work :(( I have use PF firewall and FreeBSD 6.2-RELEASE-p5. I Think this problem is from net.inet.tcp.blackhole=2 in my sysctl because it's work before i do sysctl -w net.inet.tcp.blackhole=2.. but when back this option to value = 0 this problem is stay there.. and no restarts or re-build my kernel can fix this..or maybe be wrong to this supposition. Sorry for my english. Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wierd Network problem
Craig applying the patch should be easy enough. You could always use something better than cpanel, I've always perferred directadmin myself. -- martin On 5/13/07, Craig Russell [EMAIL PROTECTED] wrote: Yes, I have tried different cables, even different physical ports (although same type of port). There was a bug filed against 6.1 for the bge interfaces that maybe related, although the bug indicated absolutely no network conductivity. There was a patch released and I'm trying to recompile with that patch. I must admit I'm having a hard time figuring out how to apply the patch but once I get past that hurdle I'll see what happens. If I can't ge the bge interface working my next best solution will be to just install another card in one of the pci slots and use that instead. Ideally, I would upgrade to 6.2 but cpanel won't support 6.2 so I'm stuck on 6.1 for the time being. Thanks for the reply, Craig Russell --- Martin Hepworth [EMAIL PROTECTED] wrote: Criag have you tried cables? Could be a duff network cable or even speed mismatch between you and the router/switch. - martin On 5/12/07, Craig Russell [EMAIL PROTECTED] wrote: I have a dell poweredge 6650 installed with freebsd 6.1 and on the local router, everything works great (ie, a computer on a different subnet off the same router can access it fine) but coming from outside of the network access is incredibly slow. My first thought was that it must be a routing issue, but I have two other freebsd 6.1 servers on that same subnet and I can access them fine from outside. I dug a little further and compared the servers that are working with those that are not and these are the differences that I have found. On the servers that are working (dell poweredge 2450's) the interface is an fxp0 and here is the output of ifconfig: fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::2b0:d0ff:fee1:f66a%fxp0 prefixlen 64 scopeid 0x1 inet 64.25.218.2 netmask 0xff80 broadcast 64.25.218.127 ether 00:b0:d0:e1:f6:6a media: Ethernet autoselect (100baseTX full-duplex) status: active on the server that is not working: bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet6 fe80::211:43ff:fedc:9aa2%bge0 prefixlen 64 scopeid 0x1 inet 64.25.218.10 netmask 0xff80 broadcast 64.25.218.127 ether 00:11:43:dc:9a:a2 media: Ethernet autoselect (100baseTX full-duplex) status: active The first thing that i noticed is that on the option line there is quite a bit of difference between the two. So using the command line ifconfig tool I removed RXCSUM, TXCSUM from the bge0 interface. Voila! Speed increased and the server was actually accessible from off net. Unfortunately, as soon as I tried to access any other port, the interface crashes. Eventually the watchdog picks up on that and restarts the interface. But the problem is completely repeatable. The server that I am having problems with is running cpanel 10.9; the two that are working are running the dns-only version of cpanel. I am not picking up any errors in the logs. This could be related to cpanel, or not, I'm not really sure, although it shouldn't be. The other unique thing about the setup, that very well may be affecting is that the router in question has two subnets configured on the internal port. There is a nat'd subnet for our local users and there is the public subnet that these servers sit on. The final resting place for all three is in a datacenter that isn't built yet, so rather than reconfigure everything once that was done I simply routed the final subnet to our office and set it up their. The router is a mikrotik RB112 board which only has one ethernet port so I couldn't dedicate a port for the new subnet. As I said, my first thought was that the problem was in the router, but the other two servers are running fine. Any suggestions? Thank you, Craig Russell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wierd Network problem
Yes, I could use something other than cpanel, and directadmin was actually one of my choices but unfortunately, that decision was not mine. I'm only responsible for getting the software that was chosen to work. My issue with the patch was that it was written for if_bge.c dated in March 2006 and I actually compiled a new kernel using the release from December 2006. Everything that I read about the bug said that it was fixed in the 6.2-release tree so I thought that would be ok. Tcpdumps did show massive amounts of bad chksum's from packets off of the network so it looks as though that was my issue. Not sure why it didn't work after the recompile. I ended up having to install a new card and a linksys gigabit card is working nicely now. Thanks for all of the suggestions. Craig Russell --- Martin Hepworth [EMAIL PROTECTED] wrote: Craig applying the patch should be easy enough. You could always use something better than cpanel, I've always perferred directadmin myself. -- martin On 5/13/07, Craig Russell [EMAIL PROTECTED] wrote: Yes, I have tried different cables, even different physical ports (although same type of port). There was a bug filed against 6.1 for the bge interfaces that maybe related, although the bug indicated absolutely no network conductivity. There was a patch released and I'm trying to recompile with that patch. I must admit I'm having a hard time figuring out how to apply the patch but once I get past that hurdle I'll see what happens. If I can't ge the bge interface working my next best solution will be to just install another card in one of the pci slots and use that instead. Ideally, I would upgrade to 6.2 but cpanel won't support 6.2 so I'm stuck on 6.1 for the time being. Thanks for the reply, Craig Russell --- Martin Hepworth [EMAIL PROTECTED] wrote: Criag have you tried cables? Could be a duff network cable or even speed mismatch between you and the router/switch. - martin On 5/12/07, Craig Russell [EMAIL PROTECTED] wrote: I have a dell poweredge 6650 installed with freebsd 6.1 and on the local router, everything works great (ie, a computer on a different subnet off the same router can access it fine) but coming from outside of the network access is incredibly slow. My first thought was that it must be a routing issue, but I have two other freebsd 6.1 servers on that same subnet and I can access them fine from outside. I dug a little further and compared the servers that are working with those that are not and these are the differences that I have found. On the servers that are working (dell poweredge 2450's) the interface is an fxp0 and here is the output of ifconfig: fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::2b0:d0ff:fee1:f66a%fxp0 prefixlen 64 scopeid 0x1 inet 64.25.218.2 netmask 0xff80 broadcast 64.25.218.127 ether 00:b0:d0:e1:f6:6a media: Ethernet autoselect (100baseTX full-duplex) status: active on the server that is not working: bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet6 fe80::211:43ff:fedc:9aa2%bge0 prefixlen 64 scopeid 0x1 inet 64.25.218.10 netmask 0xff80 broadcast 64.25.218.127 ether 00:11:43:dc:9a:a2 media: Ethernet autoselect (100baseTX full-duplex) status: active The first thing that i noticed is that on the option line there is quite a bit of difference between the two. So using the command line ifconfig tool I removed RXCSUM, TXCSUM from the bge0 interface. Voila! Speed increased and the server was actually accessible from off net. Unfortunately, as soon as I tried to access any other port, the interface crashes. Eventually the watchdog picks up on that and restarts the interface. But the problem is completely repeatable. The server that I am having problems with is running cpanel 10.9; the two that are working are running the dns-only version of cpanel. I am not picking up any errors in the logs. This could be related to cpanel, or not, I'm not really sure, although it shouldn't be. The other unique thing about the setup, that very well may be affecting is that the router in question has two subnets configured on the internal port. There is a nat'd subnet for our local users and there is the public subnet that these servers sit on. The final resting place for all three is in a datacenter that isn't built yet, so rather than reconfigure everything once that was done I simply routed the final subnet to our office and set it up their.
Re: Wierd Network problem
Criag have you tried cables? Could be a duff network cable or even speed mismatch between you and the router/switch. - martin On 5/12/07, Craig Russell [EMAIL PROTECTED] wrote: I have a dell poweredge 6650 installed with freebsd 6.1 and on the local router, everything works great (ie, a computer on a different subnet off the same router can access it fine) but coming from outside of the network access is incredibly slow. My first thought was that it must be a routing issue, but I have two other freebsd 6.1 servers on that same subnet and I can access them fine from outside. I dug a little further and compared the servers that are working with those that are not and these are the differences that I have found. On the servers that are working (dell poweredge 2450's) the interface is an fxp0 and here is the output of ifconfig: fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::2b0:d0ff:fee1:f66a%fxp0 prefixlen 64 scopeid 0x1 inet 64.25.218.2 netmask 0xff80 broadcast 64.25.218.127 ether 00:b0:d0:e1:f6:6a media: Ethernet autoselect (100baseTX full-duplex) status: active on the server that is not working: bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet6 fe80::211:43ff:fedc:9aa2%bge0 prefixlen 64 scopeid 0x1 inet 64.25.218.10 netmask 0xff80 broadcast 64.25.218.127 ether 00:11:43:dc:9a:a2 media: Ethernet autoselect (100baseTX full-duplex) status: active The first thing that i noticed is that on the option line there is quite a bit of difference between the two. So using the command line ifconfig tool I removed RXCSUM, TXCSUM from the bge0 interface. Voila! Speed increased and the server was actually accessible from off net. Unfortunately, as soon as I tried to access any other port, the interface crashes. Eventually the watchdog picks up on that and restarts the interface. But the problem is completely repeatable. The server that I am having problems with is running cpanel 10.9; the two that are working are running the dns-only version of cpanel. I am not picking up any errors in the logs. This could be related to cpanel, or not, I'm not really sure, although it shouldn't be. The other unique thing about the setup, that very well may be affecting is that the router in question has two subnets configured on the internal port. There is a nat'd subnet for our local users and there is the public subnet that these servers sit on. The final resting place for all three is in a datacenter that isn't built yet, so rather than reconfigure everything once that was done I simply routed the final subnet to our office and set it up their. The router is a mikrotik RB112 board which only has one ethernet port so I couldn't dedicate a port for the new subnet. As I said, my first thought was that the problem was in the router, but the other two servers are running fine. Any suggestions? Thank you, Craig Russell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wierd Network problem
Yes, I have tried different cables, even different physical ports (although same type of port). There was a bug filed against 6.1 for the bge interfaces that maybe related, although the bug indicated absolutely no network conductivity. There was a patch released and I'm trying to recompile with that patch. I must admit I'm having a hard time figuring out how to apply the patch but once I get past that hurdle I'll see what happens. If I can't ge the bge interface working my next best solution will be to just install another card in one of the pci slots and use that instead. Ideally, I would upgrade to 6.2 but cpanel won't support 6.2 so I'm stuck on 6.1 for the time being. Thanks for the reply, Craig Russell --- Martin Hepworth [EMAIL PROTECTED] wrote: Criag have you tried cables? Could be a duff network cable or even speed mismatch between you and the router/switch. - martin On 5/12/07, Craig Russell [EMAIL PROTECTED] wrote: I have a dell poweredge 6650 installed with freebsd 6.1 and on the local router, everything works great (ie, a computer on a different subnet off the same router can access it fine) but coming from outside of the network access is incredibly slow. My first thought was that it must be a routing issue, but I have two other freebsd 6.1 servers on that same subnet and I can access them fine from outside. I dug a little further and compared the servers that are working with those that are not and these are the differences that I have found. On the servers that are working (dell poweredge 2450's) the interface is an fxp0 and here is the output of ifconfig: fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::2b0:d0ff:fee1:f66a%fxp0 prefixlen 64 scopeid 0x1 inet 64.25.218.2 netmask 0xff80 broadcast 64.25.218.127 ether 00:b0:d0:e1:f6:6a media: Ethernet autoselect (100baseTX full-duplex) status: active on the server that is not working: bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet6 fe80::211:43ff:fedc:9aa2%bge0 prefixlen 64 scopeid 0x1 inet 64.25.218.10 netmask 0xff80 broadcast 64.25.218.127 ether 00:11:43:dc:9a:a2 media: Ethernet autoselect (100baseTX full-duplex) status: active The first thing that i noticed is that on the option line there is quite a bit of difference between the two. So using the command line ifconfig tool I removed RXCSUM, TXCSUM from the bge0 interface. Voila! Speed increased and the server was actually accessible from off net. Unfortunately, as soon as I tried to access any other port, the interface crashes. Eventually the watchdog picks up on that and restarts the interface. But the problem is completely repeatable. The server that I am having problems with is running cpanel 10.9; the two that are working are running the dns-only version of cpanel. I am not picking up any errors in the logs. This could be related to cpanel, or not, I'm not really sure, although it shouldn't be. The other unique thing about the setup, that very well may be affecting is that the router in question has two subnets configured on the internal port. There is a nat'd subnet for our local users and there is the public subnet that these servers sit on. The final resting place for all three is in a datacenter that isn't built yet, so rather than reconfigure everything once that was done I simply routed the final subnet to our office and set it up their. The router is a mikrotik RB112 board which only has one ethernet port so I couldn't dedicate a port for the new subnet. As I said, my first thought was that the problem was in the router, but the other two servers are running fine. Any suggestions? Thank you, Craig Russell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Wierd Network problem
I have a dell poweredge 6650 installed with freebsd 6.1 and on the local router, everything works great (ie, a computer on a different subnet off the same router can access it fine) but coming from outside of the network access is incredibly slow. My first thought was that it must be a routing issue, but I have two other freebsd 6.1 servers on that same subnet and I can access them fine from outside. I dug a little further and compared the servers that are working with those that are not and these are the differences that I have found. On the servers that are working (dell poweredge 2450's) the interface is an fxp0 and here is the output of ifconfig: fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::2b0:d0ff:fee1:f66a%fxp0 prefixlen 64 scopeid 0x1 inet 64.25.218.2 netmask 0xff80 broadcast 64.25.218.127 ether 00:b0:d0:e1:f6:6a media: Ethernet autoselect (100baseTX full-duplex) status: active on the server that is not working: bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet6 fe80::211:43ff:fedc:9aa2%bge0 prefixlen 64 scopeid 0x1 inet 64.25.218.10 netmask 0xff80 broadcast 64.25.218.127 ether 00:11:43:dc:9a:a2 media: Ethernet autoselect (100baseTX full-duplex) status: active The first thing that i noticed is that on the option line there is quite a bit of difference between the two. So using the command line ifconfig tool I removed RXCSUM, TXCSUM from the bge0 interface. Voila! Speed increased and the server was actually accessible from off net. Unfortunately, as soon as I tried to access any other port, the interface crashes. Eventually the watchdog picks up on that and restarts the interface. But the problem is completely repeatable. The server that I am having problems with is running cpanel 10.9; the two that are working are running the dns-only version of cpanel. I am not picking up any errors in the logs. This could be related to cpanel, or not, I'm not really sure, although it shouldn't be. The other unique thing about the setup, that very well may be affecting is that the router in question has two subnets configured on the internal port. There is a nat'd subnet for our local users and there is the public subnet that these servers sit on. The final resting place for all three is in a datacenter that isn't built yet, so rather than reconfigure everything once that was done I simply routed the final subnet to our office and set it up their. The router is a mikrotik RB112 board which only has one ethernet port so I couldn't dedicate a port for the new subnet. As I said, my first thought was that the problem was in the router, but the other two servers are running fine. Any suggestions? Thank you, Craig Russell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: network problem
Tsu-Fan Cheng [EMAIL PROTECTED] writes: I am using bt to download files and i know this is bad for netowrk... Not particularly; just make sure it isn't grabbing all of your bandwidth. sometimes my firefox returns the site not found on some popular sites, such as yahoo and google, and it looks like firefox didnt try hard enough before it gave it up. i have to ask it to reload to get it to hook up to the website. my question is, is this solely due to that i am bting, or there is something else i can do to make this better?? thanks !! It's possible that saturating your network link (in either direction) could cause DNS failures, but that isn't the most likely symptom. Running your own caching nameserver would reduce the problem in that case. And a number of other cases, come to think of it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
network problem
hi people, I am using bt to download files and i know this is bad for netowrk... anyhow.. sometimes my firefox returns the site not found on some popular sites, such as yahoo and google, and it looks like firefox didnt try hard enough before it gave it up. i have to ask it to reload to get it to hook up to the website. my question is, is this solely due to that i am bting, or there is something else i can do to make this better?? thanks !! TFC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Network problem
Background Information: FreeBSD 5.4 - Try to connect to internet (open Yahoo, mozilla), but there is no response from browser (Mozilla), it looks like stuck there. But I can ping to yahoo and mozilla. Any suggestion? Thanks, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network problem
On Sunday 12 June 2005 19:58, the author Zousys Info contributed to the dialogue on- Network problem: Background Information: FreeBSD 5.4 - Try to connect to internet (open Yahoo, mozilla), but there is no response from browser (Mozilla), it looks like stuck there. But I can ping to yahoo and mozilla. Any suggestion? Check your /etc/hosts files David -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May/June bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Network problem after upgrade from 5.1 to 5.3
Hi ! I am long time user of FreeBSD and for must updates so far I hadn't had much to do (maybe option here and option there, but networking never changes), but after upgrade from 5.1 to 5.3 everything stoped working. Since I couldn't rebuild kernel (some internal problems), I decided to delete everything and reinstal from scratch (last time I did this was when disk crashed, and that was about 5 years ago). But now again nothing works. I didn't change any configuration files since instalation except, rc.conf, and copied my firewall.conf and natd.conf... Even after recompiled I couldn't use network. My FreeBSD is used as server and also router for my internal network (using NAT). Problem: == If I disable firewall, natd is turned down so inside computers can't get to internet through FreeBSD box, if enabled, then nothing works. It seems like small trouble in Firewall, but I don't know why. I usually didn't make any changes to firewall since I am not guru there... Config: = FreeBSD BOX- dc0: external IP | V rl0: internal IP 192.168.44.1 - Hub I was using NATD and firewall (I have my own rules for both and everything worked before), I have compiled IPDIVERT and IPFIREWALL into kernel. Startup rc.conf: === defaultrouter=xx.xx.5.1 # Set to default gateway (or NO). firewall_enable=YES # Set to YES to enable firewall functionality firewall_silent=YES firewall_type=/etc/firewall.conf # Firewall type (see /etc/rc.firewall) gateway_enable=YES# Set to YES if this host will be a gateway. hostname=atechnet.dhs.org # Set this! ifconfig_dc0=inet xx.xx.5.51 netmask 255.255.255.0 ifconfig_lo0=inet 127.0.0.1 netmask 255.255.255.0 ifconfig_rl0=inet 192.168.44.1 netmask 255.255.255.0 natd_enable=YES # Enable natd (if firewall_enable ==YES). natd_flags=-s -u -f /etc/natd.conf natd_interface=dc0 network_interfaces=auto natd.conf (This is just for redirection of emule ports) === redirect_port tcp 192.168.44.2:4662 4662 redirect_port udp 192.168.44.2:4672 4672 redirect_port tcp 192.168.44.2:4711 4711 redirect_port tcp 192.168.44.1:5432 5432 redirect_port udp 192.168.44.1:5432 5432 firewall.conf (this is open firewall with added ports for redirection) = add 00050 set 0 divert 8668 ip from any to any add 00100 set 0 allow ip from any to any add 00200 set 0 deny ip from any to 127.0.0.0/8 add 00300 set 0 deny ip from 127.0.0.0/8 to any add 1 set 0 allow udp from any 4672 to 192.168.44.2 dst-port 4672 add 10001 set 0 allow tcp from any 4662 to 192.168.44.2 dst-port 4662 add 10002 set 0 allow tcp from any 4711 to 192.168.44.2 dst-port 4711 add 65000 set 0 allow ip from any to any Please help me, I need to make my server active again, but I can't do that unless whole network is working... Andy ** * Aleksander Rozman - Andy * Fandoms: E2:EA, SAABer, Trekkie, Earthie * * [EMAIL PROTECTED] * Sentinel, BH 90210, True's Trooper, * *[EMAIL PROTECTED] * Heller's Angel, Questie, Legacy, PO5, * * Maribor, Slovenia (Europe) * Profiler, Buffy (Slayerete), Pretender* * ICQ-UIC: 4911125 * * PGP key available *http://www.atechnet.dhs.org/~andy/ * ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Network problem after upgrade from 5.1 to 5.3
Hi ! I am long time user of FreeBSD and for must updates so far I hadn't had much to do (maybe option here and option there, but networking never changes), but after upgrade from 5.1 to 5.3 everything stoped working. Since I couldn't rebuild kernel (some internal problems), I decided to delete everything and reinstal from scratch (last time I did this was when disk crashed, and that was about 5 years ago). But now again nothing works. I didn't change any configuration files since instalation except, rc.conf, and copied my firewall.conf and natd.conf... Even after recompiled I couldn't use network. My FreeBSD is used as server and also router for my internal network (using NAT). Problem: == If I disable firewall, natd is turned down so inside computers can't get to internet through FreeBSD box, if enabled, then nothing works. It seems like small trouble in Firewall, but I don't know why. I usually didn't make any changes to firewall since I am not guru there... Config: = FreeBSD BOX- dc0: external IP | V rl0: internal IP 192.168.44.1 - Hub I was using NATD and firewall (I have my own rules for both and everything worked before), I have compiled IPDIVERT and IPFIREWALL into kernel. Startup rc.conf: === defaultrouter=xx.xx.5.1 # Set to default gateway (or NO). firewall_enable=YES # Set to YES to enable firewall functionality firewall_silent=YES firewall_type=/etc/firewall.conf # Firewall type (see /etc/rc.firewall) gateway_enable=YES# Set to YES if this host will be a gateway. hostname=atechnet.dhs.org # Set this! ifconfig_dc0=inet xx.xx.5.51 netmask 255.255.255.0 ifconfig_lo0=inet 127.0.0.1 netmask 255.255.255.0 ifconfig_rl0=inet 192.168.44.1 netmask 255.255.255.0 natd_enable=YES # Enable natd (if firewall_enable ==YES). natd_flags=-s -u -f /etc/natd.conf natd_interface=dc0 network_interfaces=auto natd.conf (This is just for redirection of emule ports) === redirect_port tcp 192.168.44.2:4662 4662 redirect_port udp 192.168.44.2:4672 4672 redirect_port tcp 192.168.44.2:4711 4711 redirect_port tcp 192.168.44.1:5432 5432 redirect_port udp 192.168.44.1:5432 5432 firewall.conf (this is open firewall with added ports for redirection) = add 00050 set 0 divert 8668 ip from any to any add 00100 set 0 allow ip from any to any add 00200 set 0 deny ip from any to 127.0.0.0/8 add 00300 set 0 deny ip from 127.0.0.0/8 to any add 1 set 0 allow udp from any 4672 to 192.168.44.2 dst-port 4672 add 10001 set 0 allow tcp from any 4662 to 192.168.44.2 dst-port 4662 add 10002 set 0 allow tcp from any 4711 to 192.168.44.2 dst-port 4711 add 65000 set 0 allow ip from any to any Please help me, I need to make my server active again, but I can't do that unless whole network is working... Andy ** * Aleksander Rozman - Andy * Fandoms: E2:EA, SAABer, Trekkie, Earthie * * [EMAIL PROTECTED] * Sentinel, BH 90210, True's Trooper, * *[EMAIL PROTECTED] * Heller's Angel, Questie, Legacy, PO5, * * Maribor, Slovenia (Europe) * Profiler, Buffy (Slayerete), Pretender* * ICQ-UIC: 4911125 * * PGP key available *http://www.atechnet.dhs.org/~andy/ * ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
network problem with emulators/qemu
I need to make linux (gentoo) run (emulated) under fbsd 5.3, I'm using QEMU from ports. I get host and guest pinged ok, but I can't make guest get inet. There's one thing that doesn't seem to match the info I googled (qemu-docs says this too), when QEMU starts it doesn't says Connected to host network interface: tun0, btw I can't distinguish from tun and tap, the man pages are almost equal(!?). So I've ignored this and go on with tap0 in my experiments. Im using NAT in my box (for the 192.168.0 network), and this is the line I added to ipnat.conf: map tun0 172.20.0.0/24 - 0/32... but I don't think there's the problem. Please, ask me if you need more info... I'm totally lost with this one :/ thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
network problem with emulators/qemu
I need to make linux (gentoo) run (emulated) under fbsd 5.3, I'm using QEMU from ports. I get host and guest pinged ok, but I can't make guest get inet. There's one thing that doesn't seem to match the info I googled (qemu-docs says this too), when QEMU starts it doesn't says Connected to host network interface: tun0, btw I can't distinguish from tun and tap, the man pages are almost equal(!?). So I've ignored this and go on with tap0 in my experiments. Im using NAT in my box (for the 192.168.0 network), and this is the line I added to ipnat.conf: map tun0 172.20.0.0/24 - 0/32... but I don't think there's the problem. Please, ask me if you need more info... I'm totally lost with this one :/ thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Network Problem
Hi Guys, I've been experiencing a strange problem with our FreeBSD web server: FreeBSD www.piyeepress.com 4.8-RELEASE Server version: Apache/1.3.27 (Unix) When accessed via a web browser, it will return pages for a few minutes. Eventually access is super super slow, as if some TCP state table is filling up. I reboot the server and it returns web pages as it should, but only for five or so minutes, when it won't return any more pages, or it returns pages but very slowly. I've tailed the apache log and the page is returned when I see it appear in my web browser. I'll click on a link, wait a minute or so, and if the page does finally appear in the browser, only then do I see the access in the httpd log. Same type of thing with tcpdump. Using rules and a few regular expressions to show just my IP, I don't see anything until the actual webpage comes through on my screen. The output of netstat -ap tcp doesn't show too many open states. I swear that some tcp state table is filling up; otherwise I have no clues. Here's something too: if I use lynx to access the site, and I access the site from another server in the same rack, the page is returned instantly. Here's some more confusion: non-Windows machines seem to do better at getting pages from the server than do Windows machines. Any ideas? Sorry if I have been unclear. This problem has been driving me crazy! Thanks, Chris Kelly +-+ Christopher Kelly Webmaster, Pi Yee Press 4855 W. Nevso Drive Las Vegas, NV 89103 [EMAIL PROTECTED] Office - (702) 579-7711 Fax - (702) 579-BOOK +-+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Problem
On Wed, 15 Dec 2004, Chris Kelly wrote: FreeBSD www.piyeepress.com 4.8-RELEASE Pretty old... Server version: Apache/1.3.27 (Unix) Quite old for Apache, and with some known security vulnerabilities, I think. When accessed via a web browser, it will return pages for a few minutes. Eventually access is super super slow, as if some TCP state table is filling up. I reboot the server and it returns web pages as it should, but only for five or so minutes, when it won't return any more pages, or it returns pages but very slowly. It may not be a network problem. The output of netstat -ap tcp doesn't show too many open states. I swear that some tcp state table is filling up; otherwise I have no clues. Here's something too: if I use lynx to access the site, and I access the site from another server in the same rack, the page is returned instantly. Here's some more confusion: non-Windows machines seem to do better at getting pages from the server than do Windows machines. A router choking? Some kind of firewall problem? Either way, I'd still suggest updating to 4.10 and Apache 1.3.33 for a start. -Warren Block * Rapid City, South Dakota USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
new 5.1 install network problem.
Please help me troubleshoot a network problem. In the past, after installing, it has all just worked, so I'm not sure exactly how to best proceed. When the PC was formatted as Win98 the network connection worked fine, and the cabling is on my work bench and works fine on other test systems, so I don't suspect a hardware problem. I just installed 5.1 from the CD's on to an IBM Aptiva E96. It has a 3Com 3C905B-TXNM card, which seems to have been correctly identified. On Boot things seem to proceed normally until the Sendmail message where the boot seems to stop for several minutes. (I thought I selected to not enable sendmail ) Name resolution is not working and the network connection seems to be timing out a lot as all network functions are very sluggish. For instance, I CAN ping the IP of my name server, however even though the response is less than 1ms, there is about 80% packet loss. nslookup can't connect to the name server, even using IP, and again I suspect that it is timing out. Was able to connect to my FTP server using its IP to try to transfer some files, for this email, but the connection timed out nd was reset when trying to cd to the input directory. Here are what I think are the relevant lines from my messages log where the card is found on boot: Dec 22 09:16:27 fbsd04 kernel: xl0: 3Com 3c905B-TX Fast Etherlink XL port 0x7080-0x70ff mem 0x8010-0x8010007f irq 10 at device 13.0 on pci0 Dec 22 09:16:27 fbsd04 kernel: xl0: Ethernet address: 00:10:5a:a0:ce:0b Dec 22 09:16:27 fbsd04 kernel: miibus0: MII bus on xl0 Dec 22 09:16:27 fbsd04 kernel: xlphy0: 3Com internal media interface on miibus0 Dec 22 09:16:27 fbsd04 kernel: xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Here is output from ifconfig with the IPs obscured, but the IP looks good to me: xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet ###.###.###.### netmask 0x broadcast ###.###.###.### inet6 fe80::210:5aff:fea0:ce0b%xl0 prefixlen 64 scopeid 0x1 ether 00:10:5a:a0:ce:0b media: Ethernet autoselect (100baseTX full-duplex) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 Any ideas/suggestions? Thanks, Cla. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: new 5.1 install network problem.
You are correct, sure sounds like DNS time out problem. Do you have hostname='gateway.fakeDOMAINname.com' in rc.conf Do you have entry in /etc/hosts file for ip address of Nic card and it's FQDN IE: 'gateway.fakeDOMAINname.com' If this PC is connected to lan, does the lan use DHCP, and if so do you have ifconfig_xl0=DHCP in rc.conf? Check /etc/resolv.conf to see that it has the IP address of your ISP DNS severs. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Clarence Brown Sent: Monday, December 22, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: new 5.1 install network problem. Please help me troubleshoot a network problem. In the past, after installing, it has all just worked, so I'm not sure exactly how to best proceed. When the PC was formatted as Win98 the network connection worked fine, and the cabling is on my work bench and works fine on other test systems, so I don't suspect a hardware problem. I just installed 5.1 from the CD's on to an IBM Aptiva E96. It has a 3Com 3C905B-TXNM card, which seems to have been correctly identified. On Boot things seem to proceed normally until the Sendmail message where the boot seems to stop for several minutes. (I thought I selected to not enable sendmail ) Name resolution is not working and the network connection seems to be timing out a lot as all network functions are very sluggish. For instance, I CAN ping the IP of my name server, however even though the response is less than 1ms, there is about 80% packet loss. nslookup can't connect to the name server, even using IP, and again I suspect that it is timing out. Was able to connect to my FTP server using its IP to try to transfer some files, for this email, but the connection timed out nd was reset when trying to cd to the input directory. Here are what I think are the relevant lines from my messages log where the card is found on boot: Dec 22 09:16:27 fbsd04 kernel: xl0: 3Com 3c905B-TX Fast Etherlink XL port 0x7080-0x70ff mem 0x8010-0x8010007f irq 10 at device 13.0 on pci0 Dec 22 09:16:27 fbsd04 kernel: xl0: Ethernet address: 00:10:5a:a0:ce:0b Dec 22 09:16:27 fbsd04 kernel: miibus0: MII bus on xl0 Dec 22 09:16:27 fbsd04 kernel: xlphy0: 3Com internal media interface on miibus0 Dec 22 09:16:27 fbsd04 kernel: xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Here is output from ifconfig with the IPs obscured, but the IP looks good to me: xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet ###.###.###.### netmask 0x broadcast ###.###.###.### inet6 fe80::210:5aff:fea0:ce0b%xl0 prefixlen 64 scopeid 0x1 ether 00:10:5a:a0:ce:0b media: Ethernet autoselect (100baseTX full-duplex) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 Any ideas/suggestions? Thanks, Cla. ___ [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: new 5.1 install network problem.
Thanks for the Reply: I believe that the DNS timeout is a symptom rather than cause of the problem, because I'm getting an 80% packet loss when pinging the IP address of the DNS server. I'm running the DNS servers, and they are on the same LAN. resolv.conf is same on this machine as on other machines that do work. The LAN does have DHCP, but I assigned this FreeBSD machine a static IP at an unused address in a range of addresses that I have reserved for servers. in rc.conf (the ip addresses are the values I expect): defaultrouter=###.###.###.### hostname=fbsd04.fakeDOMAINname.com ifconfig_xl0=inet ###.###.###.### netmask ###.###.###.### in hosts, I had to add the correct domain to localhost, and add entries for the machine's own name, but this didn't seem to help. With further testing, still getting 60%-80% packet loss when trying to ping IP address of other machines on network from problem machine, but some DO get through. Other machines are getting similar results when trying to ping the IP address of the problem machine. Thanks again, Cla. - Original Message - From: fbsd_user [EMAIL PROTECTED] To: Clarence Brown [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, December 22, 2003 11:07 AM Subject: RE: new 5.1 install network problem. You are correct, sure sounds like DNS time out problem. Do you have hostname='gateway.fakeDOMAINname.com' in rc.conf Do you have entry in /etc/hosts file for ip address of Nic card and it's FQDN IE: 'gateway.fakeDOMAINname.com' If this PC is connected to lan, does the lan use DHCP, and if so do you have ifconfig_xl0=DHCP in rc.conf? Check /etc/resolv.conf to see that it has the IP address of your ISP DNS severs. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Clarence Brown Sent: Monday, December 22, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: new 5.1 install network problem. Please help me troubleshoot a network problem. In the past, after installing, it has all just worked, so I'm not sure exactly how to best proceed. When the PC was formatted as Win98 the network connection worked fine, and the cabling is on my work bench and works fine on other test systems, so I don't suspect a hardware problem. I just installed 5.1 from the CD's on to an IBM Aptiva E96. It has a 3Com 3C905B-TXNM card, which seems to have been correctly identified. On Boot things seem to proceed normally until the Sendmail message where the boot seems to stop for several minutes. (I thought I selected to not enable sendmail ) Name resolution is not working and the network connection seems to be timing out a lot as all network functions are very sluggish. For instance, I CAN ping the IP of my name server, however even though the response is less than 1ms, there is about 80% packet loss. nslookup can't connect to the name server, even using IP, and again I suspect that it is timing out. Was able to connect to my FTP server using its IP to try to transfer some files, for this email, but the connection timed out nd was reset when trying to cd to the input directory. Here are what I think are the relevant lines from my messages log where the card is found on boot: Dec 22 09:16:27 fbsd04 kernel: xl0: 3Com 3c905B-TX Fast Etherlink XL port 0x7080-0x70ff mem 0x8010-0x8010007f irq 10 at device 13.0 on pci0 Dec 22 09:16:27 fbsd04 kernel: xl0: Ethernet address: 00:10:5a:a0:ce:0b Dec 22 09:16:27 fbsd04 kernel: miibus0: MII bus on xl0 Dec 22 09:16:27 fbsd04 kernel: xlphy0: 3Com internal media interface on miibus0 Dec 22 09:16:27 fbsd04 kernel: xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Here is output from ifconfig with the IPs obscured, but the IP looks good to me: xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet ###.###.###.### netmask 0x broadcast ###.###.###.### inet6 fe80::210:5aff:fea0:ce0b%xl0 prefixlen 64 scopeid 0x1 ether 00:10:5a:a0:ce:0b media: Ethernet autoselect (100baseTX full-duplex) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 Any ideas/suggestions? Thanks, Cla. ___ [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: new 5.1 install network problem.
Clarence Brown wrote: Thanks for the Reply: I believe that the DNS timeout is a symptom rather than cause of the problem, because I'm getting an 80% packet loss when pinging the IP address of the DNS server. I'm running the DNS servers, and they are on the same LAN. I've seen this type of response when there is a mismatch of autosensing network adapters. Try forcing your network card to whatever speed and duplex setting you prefer to run at and make sure that the switch port your connected to is set the same. The machine you're configuring is at full-duplex, but the switch may be at half duplex. resolv.conf is same on this machine as on other machines that do work. The LAN does have DHCP, but I assigned this FreeBSD machine a static IP at an unused address in a range of addresses that I have reserved for servers. in rc.conf (the ip addresses are the values I expect): defaultrouter=###.###.###.### hostname=fbsd04.fakeDOMAINname.com ifconfig_xl0=inet ###.###.###.### netmask ###.###.###.### in hosts, I had to add the correct domain to localhost, and add entries for the machine's own name, but this didn't seem to help. With further testing, still getting 60%-80% packet loss when trying to ping IP address of other machines on network from problem machine, but some DO get through. Other machines are getting similar results when trying to ping the IP address of the problem machine. Thanks again, Cla. - Original Message - From: fbsd_user [EMAIL PROTECTED] To: Clarence Brown [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, December 22, 2003 11:07 AM Subject: RE: new 5.1 install network problem. You are correct, sure sounds like DNS time out problem. Do you have hostname='gateway.fakeDOMAINname.com' in rc.conf Do you have entry in /etc/hosts file for ip address of Nic card and it's FQDN IE: 'gateway.fakeDOMAINname.com' If this PC is connected to lan, does the lan use DHCP, and if so do you have ifconfig_xl0=DHCP in rc.conf? Check /etc/resolv.conf to see that it has the IP address of your ISP DNS severs. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Clarence Brown Sent: Monday, December 22, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: new 5.1 install network problem. Please help me troubleshoot a network problem. In the past, after installing, it has all just worked, so I'm not sure exactly how to best proceed. When the PC was formatted as Win98 the network connection worked fine, and the cabling is on my work bench and works fine on other test systems, so I don't suspect a hardware problem. I just installed 5.1 from the CD's on to an IBM Aptiva E96. It has a 3Com 3C905B-TXNM card, which seems to have been correctly identified. On Boot things seem to proceed normally until the Sendmail message where the boot seems to stop for several minutes. (I thought I selected to not enable sendmail ) Name resolution is not working and the network connection seems to be timing out a lot as all network functions are very sluggish. For instance, I CAN ping the IP of my name server, however even though the response is less than 1ms, there is about 80% packet loss. nslookup can't connect to the name server, even using IP, and again I suspect that it is timing out. Was able to connect to my FTP server using its IP to try to transfer some files, for this email, but the connection timed out nd was reset when trying to cd to the input directory. Here are what I think are the relevant lines from my messages log where the card is found on boot: Dec 22 09:16:27 fbsd04 kernel: xl0: 3Com 3c905B-TX Fast Etherlink XL port 0x7080-0x70ff mem 0x8010-0x8010007f irq 10 at device 13.0 on pci0 Dec 22 09:16:27 fbsd04 kernel: xl0: Ethernet address: 00:10:5a:a0:ce:0b Dec 22 09:16:27 fbsd04 kernel: miibus0: MII bus on xl0 Dec 22 09:16:27 fbsd04 kernel: xlphy0: 3Com internal media interface on miibus0 Dec 22 09:16:27 fbsd04 kernel: xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Here is output from ifconfig with the IPs obscured, but the IP looks good to me: xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet ###.###.###.### netmask 0x broadcast ###.###.###.### inet6 fe80::210:5aff:fea0:ce0b%xl0 prefixlen 64 scopeid 0x1 ether 00:10:5a:a0:ce:0b media: Ethernet autoselect (100baseTX full-duplex) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 Any ideas/suggestions? Thanks, Cla. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new 5.1 install network problem.
Thanks for the Reply: No, I hadn't checked, but the autosensing looks good. Both the card and switch are at 100 and full-duplex. Thanks again, Cla. - Original Message - From: Mike Gruen [EMAIL PROTECTED] To: Clarence Brown [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, December 22, 2003 12:35 PM Subject: Re: new 5.1 install network problem. Clarence Brown wrote: Thanks for the Reply: I believe that the DNS timeout is a symptom rather than cause of the problem, because I'm getting an 80% packet loss when pinging the IP address of the DNS server. I'm running the DNS servers, and they are on the same LAN. I've seen this type of response when there is a mismatch of autosensing network adapters. Try forcing your network card to whatever speed and duplex setting you prefer to run at and make sure that the switch port your connected to is set the same. The machine you're configuring is at full-duplex, but the switch may be at half duplex. resolv.conf is same on this machine as on other machines that do work. The LAN does have DHCP, but I assigned this FreeBSD machine a static IP at an unused address in a range of addresses that I have reserved for servers. in rc.conf (the ip addresses are the values I expect): defaultrouter=###.###.###.### hostname=fbsd04.fakeDOMAINname.com ifconfig_xl0=inet ###.###.###.### netmask ###.###.###.### in hosts, I had to add the correct domain to localhost, and add entries for the machine's own name, but this didn't seem to help. With further testing, still getting 60%-80% packet loss when trying to ping IP address of other machines on network from problem machine, but some DO get through. Other machines are getting similar results when trying to ping the IP address of the problem machine. Thanks again, Cla. - Original Message - From: fbsd_user [EMAIL PROTECTED] To: Clarence Brown [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, December 22, 2003 11:07 AM Subject: RE: new 5.1 install network problem. You are correct, sure sounds like DNS time out problem. Do you have hostname='gateway.fakeDOMAINname.com' in rc.conf Do you have entry in /etc/hosts file for ip address of Nic card and it's FQDN IE: 'gateway.fakeDOMAINname.com' If this PC is connected to lan, does the lan use DHCP, and if so do you have ifconfig_xl0=DHCP in rc.conf? Check /etc/resolv.conf to see that it has the IP address of your ISP DNS severs. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Clarence Brown Sent: Monday, December 22, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: new 5.1 install network problem. Please help me troubleshoot a network problem. In the past, after installing, it has all just worked, so I'm not sure exactly how to best proceed. When the PC was formatted as Win98 the network connection worked fine, and the cabling is on my work bench and works fine on other test systems, so I don't suspect a hardware problem. I just installed 5.1 from the CD's on to an IBM Aptiva E96. It has a 3Com 3C905B-TXNM card, which seems to have been correctly identified. On Boot things seem to proceed normally until the Sendmail message where the boot seems to stop for several minutes. (I thought I selected to not enable sendmail ) Name resolution is not working and the network connection seems to be timing out a lot as all network functions are very sluggish. For instance, I CAN ping the IP of my name server, however even though the response is less than 1ms, there is about 80% packet loss. nslookup can't connect to the name server, even using IP, and again I suspect that it is timing out. Was able to connect to my FTP server using its IP to try to transfer some files, for this email, but the connection timed out nd was reset when trying to cd to the input directory. Here are what I think are the relevant lines from my messages log where the card is found on boot: Dec 22 09:16:27 fbsd04 kernel: xl0: 3Com 3c905B-TX Fast Etherlink XL port 0x7080-0x70ff mem 0x8010-0x8010007f irq 10 at device 13.0 on pci0 Dec 22 09:16:27 fbsd04 kernel: xl0: Ethernet address: 00:10:5a:a0:ce:0b Dec 22 09:16:27 fbsd04 kernel: miibus0: MII bus on xl0 Dec 22 09:16:27 fbsd04 kernel: xlphy0: 3Com internal media interface on miibus0 Dec 22 09:16:27 fbsd04 kernel: xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Here is output from ifconfig with the IPs obscured, but the IP looks good to me: xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet ###.###.###.### netmask 0x broadcast ###.###.###.### inet6 fe80::210:5aff:fea0:ce0b%xl0 prefixlen 64 scopeid 0x1 ether 00:10:5a:a0:ce:0b media: Ethernet autoselect (100baseTX full-duplex) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP
Re: new 5.1 install network problem.
Name resolution is not working and the network connection seems to be timing out a lot as all network functions are very sluggish. For instance, I CAN ping the IP of my name server, however even though the response is less than 1ms, there is about 80% packet loss. i was having a very similar problem a while ago. losing 33% of my pings but in my case i couldn't download past 1024 bytes of anything and that not often. in my case it turned out to be a dodgy cable... some kind of internal wire smudge that meant although it looked like a full connection (all lights on etc) it just didn't work with my cards (except on my Mac, which took it fine). have you tried changing the cable? g Thanks for the Reply: No, I hadn't checked, but the autosensing looks good. Both the card and switch are at 100 and full-duplex. Thanks again, Cla. - Original Message - From: Mike Gruen [EMAIL PROTECTED] To: Clarence Brown [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, December 22, 2003 12:35 PM Subject: Re: new 5.1 install network problem. Clarence Brown wrote: Thanks for the Reply: I believe that the DNS timeout is a symptom rather than cause of the problem, because I'm getting an 80% packet loss when pinging the IP address of the DNS server. I'm running the DNS servers, and they are on the same LAN. I've seen this type of response when there is a mismatch of autosensing network adapters. Try forcing your network card to whatever speed and duplex setting you prefer to run at and make sure that the switch port your connected to is set the same. The machine you're configuring is at full-duplex, but the switch may be at half duplex. resolv.conf is same on this machine as on other machines that do work. The LAN does have DHCP, but I assigned this FreeBSD machine a static IP at an unused address in a range of addresses that I have reserved for servers. in rc.conf (the ip addresses are the values I expect): defaultrouter=###.###.###.### hostname=fbsd04.fakeDOMAINname.com ifconfig_xl0=inet ###.###.###.### netmask ###.###.###.### in hosts, I had to add the correct domain to localhost, and add entries for the machine's own name, but this didn't seem to help. With further testing, still getting 60%-80% packet loss when trying to ping IP address of other machines on network from problem machine, but some DO get through. Other machines are getting similar results when trying to ping the IP address of the problem machine. Thanks again, Cla. - Original Message - From: fbsd_user [EMAIL PROTECTED] To: Clarence Brown [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, December 22, 2003 11:07 AM Subject: RE: new 5.1 install network problem. You are correct, sure sounds like DNS time out problem. Do you have hostname='gateway.fakeDOMAINname.com' in rc.conf Do you have entry in /etc/hosts file for ip address of Nic card and it's FQDN IE: 'gateway.fakeDOMAINname.com' If this PC is connected to lan, does the lan use DHCP, and if so do you have ifconfig_xl0=DHCP in rc.conf? Check /etc/resolv.conf to see that it has the IP address of your ISP DNS severs. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Clarence Brown Sent: Monday, December 22, 2003 10:16 AM To: [EMAIL PROTECTED] Subject: new 5.1 install network problem. Please help me troubleshoot a network problem. In the past, after installing, it has all just worked, so I'm not sure exactly how to best proceed. When the PC was formatted as Win98 the network connection worked fine, and the cabling is on my work bench and works fine on other test systems, so I don't suspect a hardware problem. I just installed 5.1 from the CD's on to an IBM Aptiva E96. It has a 3Com 3C905B-TXNM card, which seems to have been correctly identified. On Boot things seem to proceed normally until the Sendmail message where the boot seems to stop for several minutes. (I thought I selected to not enable sendmail ) Name resolution is not working and the network connection seems to be timing out a lot as all network functions are very sluggish. For instance, I CAN ping the IP of my name server, however even though the response is less than 1ms, there is about 80% packet loss. nslookup can't connect to the name server, even using IP, and again I suspect that it is timing out. Was able to connect to my FTP server using its IP to try to transfer some files, for this email, but the connection timed out nd was reset when trying to cd to the input directory. Here are what I think are the relevant lines from my messages log where the card is found on boot: Dec 22 09:16:27 fbsd04 kernel: xl0: 3Com 3c905B-TX Fast Etherlink XL port 0x7080-0x70ff mem 0x8010-0x8010007f irq 10 at device 13.0 on pci0 Dec 22
Re: STrange network problem
Hi Rus, looks like you added an alias beyond the usable range. inet 63.247.81.167 netmask 0x broadcast 63.247.81.167 is your broadcast. --WEs On Oct 20, 2003, at 12:43 PM, Rus Foster wrote: Hi All, I've just tried to bring up a new IP alias and am having trouble using it Currently ls512# ifconfig -a vr0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 63.247.81.162 netmask 0xfff8 broadcast 63.247.81.167 inet6 fe80::230:1bff:fe37:fb48%vr0 prefixlen 64 scopeid 0x1 inet 63.247.81.163 netmask 0x broadcast 63.247.81.163 inet 63.247.81.164 netmask 0x broadcast 63.247.81.164 inet 63.247.81.165 netmask 0x broadcast 63.247.81.165 inet 63.247.81.166 netmask 0x broadcast 63.247.81.166 inet 63.247.81.167 netmask 0x broadcast 63.247.81.167 ether 00:30:1b:37:fb:48 media: Ethernet autoselect (100baseTX full-duplex) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 faith0: flags=8002BROADCAST,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500 sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552 ls512# ping 63.247.81.167 PING 63.247.81.167 (63.247.81.167): 56 data bytes ping: sendto: Can't assign requested address ping: sendto: Can't assign requested address ping: sendto: Can't assign requested address ping: sendto: Can't assign requested address ^C --- 63.247.81.167 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss but ... ls512# ping 63.247.81.166 PING 63.247.81.166 (63.247.81.166): 56 data bytes 64 bytes from 63.247.81.166: icmp_seq=0 ttl=64 time=0.048 ms 64 bytes from 63.247.81.166: icmp_seq=1 ttl=64 time=0.031 ms ^C --- 63.247.81.166 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.031/0.040/0.048/0.009 ms ls512# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default63.247.81.161 UGSc 9891635vr0 63.247.81.160/29 link#1 UC 10vr0 63.247.81.161 00:0a:8a:f2:e1:00 UHLW 950vr0 1188 63.247.81.163 00:30:1b:37:fb:48 UHLW231131lo0 = 63.247.81.163/32 link#1 UC 10vr0 63.247.81.164 00:30:1b:37:fb:48 UHLW268201lo0 = 63.247.81.164/32 link#1 UC 10vr0 63.247.81.165 00:30:1b:37:fb:48 UHLW2 2336lo0 = 63.247.81.165/32 link#1 UC 10vr0 63.247.81.166 00:30:1b:37:fb:48 UHLW04lo0 = 63.247.81.166/32 link#1 UC 10vr0 63.247.81.167 00:30:1b:37:fb:48 UHLWb 0 27lo0 = 63.247.81.167/32 link#1 UC 10vr0 127.0.0.1 127.0.0.1 UH 0 48lo0 Any ideas? Nothing in dmesg Nothing in /var/log/messages rus -- w: http://www.jvps.com | Virtual Dedicated Servers from $15/mo e: [EMAIL PROTECTED]| Dontations made to Debian, FreeBSD t: +44 7919 373537 | and Slackware t: 1-888-327-6330 | email: [EMAIL PROTECTED] ___ [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: STrange network problem
You show 167 as a broadcast on the first IP line then try to use it also as an available ip On Mon, 20 Oct 2003, Rus Foster wrote: Hi All, I've just tried to bring up a new IP alias and am having trouble using it Currently ls512# ifconfig -a vr0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 63.247.81.162 netmask 0xfff8 broadcast 63.247.81.167 inet6 fe80::230:1bff:fe37:fb48%vr0 prefixlen 64 scopeid 0x1 inet 63.247.81.163 netmask 0x broadcast 63.247.81.163 inet 63.247.81.164 netmask 0x broadcast 63.247.81.164 inet 63.247.81.165 netmask 0x broadcast 63.247.81.165 inet 63.247.81.166 netmask 0x broadcast 63.247.81.166 inet 63.247.81.167 netmask 0x broadcast 63.247.81.167 ether 00:30:1b:37:fb:48 media: Ethernet autoselect (100baseTX full-duplex) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 faith0: flags=8002BROADCAST,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500 sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552 ls512# ping 63.247.81.167 PING 63.247.81.167 (63.247.81.167): 56 data bytes ping: sendto: Can't assign requested address ping: sendto: Can't assign requested address ping: sendto: Can't assign requested address ping: sendto: Can't assign requested address ^C --- 63.247.81.167 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss but ... ls512# ping 63.247.81.166 PING 63.247.81.166 (63.247.81.166): 56 data bytes 64 bytes from 63.247.81.166: icmp_seq=0 ttl=64 time=0.048 ms 64 bytes from 63.247.81.166: icmp_seq=1 ttl=64 time=0.031 ms ^C --- 63.247.81.166 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.031/0.040/0.048/0.009 ms ls512# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default63.247.81.161 UGSc 9891635vr0 63.247.81.160/29 link#1 UC 10vr0 63.247.81.161 00:0a:8a:f2:e1:00 UHLW 950vr0 1188 63.247.81.163 00:30:1b:37:fb:48 UHLW231131lo0 = 63.247.81.163/32 link#1 UC 10vr0 63.247.81.164 00:30:1b:37:fb:48 UHLW268201lo0 = 63.247.81.164/32 link#1 UC 10vr0 63.247.81.165 00:30:1b:37:fb:48 UHLW2 2336lo0 = 63.247.81.165/32 link#1 UC 10vr0 63.247.81.166 00:30:1b:37:fb:48 UHLW04lo0 = 63.247.81.166/32 link#1 UC 10vr0 63.247.81.167 00:30:1b:37:fb:48 UHLWb 0 27lo0 = 63.247.81.167/32 link#1 UC 10vr0 127.0.0.1 127.0.0.1 UH 0 48lo0 Any ideas? Nothing in dmesg Nothing in /var/log/messages rus -- w: http://www.jvps.com | Virtual Dedicated Servers from $15/mo e: [EMAIL PROTECTED]| Dontations made to Debian, FreeBSD t: +44 7919 373537| and Slackware t: 1-888-327-6330 | email: [EMAIL PROTECTED] ___ [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: Network Problem on FreeBSD-4.8 : Cannot ping LAN hosts
hi josh, thanks for the advise. it's the FIREWALL thing that don't allow my FreeBSD to access the Internet Sharing in the Windows XP. Now, its ok already. I just unchecked the option that Restricts IP hosts from Internet (external) to access the Internet Sharing Machine or something like that. Now its working. It really is not a problem with my FreeBSD LAN card or other configurations. It's the WindowsXP trick! -edwin --- Josh Paetzel [EMAIL PROTECTED] wrote: On Thu, Sep 18, 2003 at 10:04:15AM -0700, Edwin D. Vinas wrote: hi josh, see dmesg, ifconfig and netstat below... hope you can help me now. -edwin IFCONFIG dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.6 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80::280:adff:fe00:591a%dc0 prefixlen 64 scopeid 0x1 ether 00:80:ad:00:59:1a media: Ethernet autoselect (100baseTX) status: active Nothing wrong here. DMESG dc0: Davicom DM9102A 10/100BaseTX port 0xd000-0xd0ff mem 0xef00-0xefff irq 11 at device 9.0 on pci0 dc0: Ethernet address: 00:80:ad:00:59:1a miibus0: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto There's your NIC being detected. ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) falling back to PIO mode This isn't so good, looks like your hard drive is sick, although I doubt that has anything to do with your network troubles. NETSTAT -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.0.1 UGSc 0 0 dc0 127.0.0.1 127.0.0.1 UH 0 0 lo0 192.168.0 link#1 UC 1 0 dc0 192.168.0.1 link#1 UHLW 1 3 dc0 You've got the correct gateway here, and it appears to be up as well. I can browse the web using all the WinXPs but I cannot access the web via FreeBSD. FreeBSD's IP address follows the 192.198.0.x format just like the other WinXPs. When I check the FreeBSD, i can see its IP address and Subnet Mask etc via ifconfig. I can even change the IP address+ Gateway (which is WinXP2's IP add) using ifconfig or /stand/sysinstall. I even manually edited rc.conf, and even changed the setting to DHCP etc etc etc. My diagnosis tells that I cannot ping any WinXP machine in the LAN. But I can ping myself (FreeBSD) locally. When I run netstat -rn, It seems the network card is ok. When I run tcpdump, I didn't show any output. By the way, this network card is CNet PRO200. I was thinking it was not recognize or supported by the FreeBSD-4.8. When I checked FreeBSD-4.8's Hardware Compatibility Lit, I didn't see any CNet PRO200 but I saw a CNet/PRO which I suppose are just the same. So, I recompiled my Kernel again just in case FreeBSD didn't recognize this newly installed Cnet LAN card. But, nothing changed after Kernel recompilation. (But I did not change any option in the Generic kernel; just re-compiled it). The output when I ping WinXP3: ping: sendto: Host is down. It's not true coz Im typing this email right in the WinXP3 machine. I cannot also ping FreeBSD's IP add from the WinXP internet sharing server. The dmesg shows the following: pci0 (vendor=0x1106 dev=0x3059) at 17.5 irq 5. By the way, this machine where FreeBSD is installed also has WinXP which works fine when in Windows. So Im sure my LAN card is really ok. It's only a problem of FreeBSD. What should I do? I don't want to make FreeBSD machine as my Internet sharing server as of now (although its the best option). Im testing/running a Unix program that needs to be connected to the Internet via Windows XP gateway. Please help me make my FreeBSD be part of my LAN -Edwin The output of dmesg and ifconfig would be helpful in diagnosing this. I suppose that's major PITA though considering you're LAN isn't working. At the very least, the first entry that comes up with ifconfig would be very helpful. Josh Two things come to mind. One is that you don't have correct nameservers in /etc/resolv.conf. The other is that your WinXP box has it's native firewall turned on and is not playing nicely with FreeBSD. Other than that, from what I can tell everything looks ok on the FreeBSD side of things, but I agree it's odd that the same box with WinXP on it can access the network and internet just fine. One last thing I can recommend is to try arp -a and see if you are connected below the TCP level. You should get an output similar to: (10.0.0.1) at 00:02:b3:c0:a9:c9 on xl0 [ethernet] Sorry I can't be of
Re: Network Problem on FreeBSD-4.8 : Cannot ping LAN hosts
On Thu, Sep 18, 2003 at 10:04:15AM -0700, Edwin D. Vinas wrote: hi josh, see dmesg, ifconfig and netstat below... hope you can help me now. -edwin IFCONFIG dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.6 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80::280:adff:fe00:591a%dc0 prefixlen 64 scopeid 0x1 ether 00:80:ad:00:59:1a media: Ethernet autoselect (100baseTX) status: active Nothing wrong here. DMESG dc0: Davicom DM9102A 10/100BaseTX port 0xd000-0xd0ff mem 0xef00-0xefff irq 11 at device 9.0 on pci0 dc0: Ethernet address: 00:80:ad:00:59:1a miibus0: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto There's your NIC being detected. ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) falling back to PIO mode This isn't so good, looks like your hard drive is sick, although I doubt that has anything to do with your network troubles. NETSTAT -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.0.1 UGSc 0 0 dc0 127.0.0.1 127.0.0.1 UH 0 0 lo0 192.168.0 link#1 UC 1 0 dc0 192.168.0.1 link#1 UHLW 1 3 dc0 You've got the correct gateway here, and it appears to be up as well. I can browse the web using all the WinXPs but I cannot access the web via FreeBSD. FreeBSD's IP address follows the 192.198.0.x format just like the other WinXPs. When I check the FreeBSD, i can see its IP address and Subnet Mask etc via ifconfig. I can even change the IP address+ Gateway (which is WinXP2's IP add) using ifconfig or /stand/sysinstall. I even manually edited rc.conf, and even changed the setting to DHCP etc etc etc. My diagnosis tells that I cannot ping any WinXP machine in the LAN. But I can ping myself (FreeBSD) locally. When I run netstat -rn, It seems the network card is ok. When I run tcpdump, I didn't show any output. By the way, this network card is CNet PRO200. I was thinking it was not recognize or supported by the FreeBSD-4.8. When I checked FreeBSD-4.8's Hardware Compatibility Lit, I didn't see any CNet PRO200 but I saw a CNet/PRO which I suppose are just the same. So, I recompiled my Kernel again just in case FreeBSD didn't recognize this newly installed Cnet LAN card. But, nothing changed after Kernel recompilation. (But I did not change any option in the Generic kernel; just re-compiled it). The output when I ping WinXP3: ping: sendto: Host is down. It's not true coz Im typing this email right in the WinXP3 machine. I cannot also ping FreeBSD's IP add from the WinXP internet sharing server. The dmesg shows the following: pci0 (vendor=0x1106 dev=0x3059) at 17.5 irq 5. By the way, this machine where FreeBSD is installed also has WinXP which works fine when in Windows. So Im sure my LAN card is really ok. It's only a problem of FreeBSD. What should I do? I don't want to make FreeBSD machine as my Internet sharing server as of now (although its the best option). Im testing/running a Unix program that needs to be connected to the Internet via Windows XP gateway. Please help me make my FreeBSD be part of my LAN -Edwin The output of dmesg and ifconfig would be helpful in diagnosing this. I suppose that's major PITA though considering you're LAN isn't working. At the very least, the first entry that comes up with ifconfig would be very helpful. Josh Two things come to mind. One is that you don't have correct nameservers in /etc/resolv.conf. The other is that your WinXP box has it's native firewall turned on and is not playing nicely with FreeBSD. Other than that, from what I can tell everything looks ok on the FreeBSD side of things, but I agree it's odd that the same box with WinXP on it can access the network and internet just fine. One last thing I can recommend is to try arp -a and see if you are connected below the TCP level. You should get an output similar to: (10.0.0.1) at 00:02:b3:c0:a9:c9 on xl0 [ethernet] Sorry I can't be of more help but it looks like you've configured FreeBSD correctly. Josh ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Network Problem on FreeBSD-4.8 : Cannot ping LAN hosts
Hi, I've stumbling with all the mailing lists about this problem and I hope somebody will give a kind advise. Here's my LAN setup: | | || | WinXP1 WinXP2 WinXP3 WinXP4 FreeBSD WinXP3 is my Internet Sharing Machine connected to my ISP. I can browse the web using all the WinXPs but I cannot access the web via FreeBSD. FreeBSD's IP address follows the 192.198.0.x format just like the other WinXPs. When I check the FreeBSD, i can see its IP address and Subnet Mask etc via ifconfig. I can even change the IP address+ Gateway (which is WinXP2's IP add) using ifconfig or /stand/sysinstall. I even manually edited rc.conf, and even changed the setting to DHCP etc etc etc. My diagnosis tells that I cannot ping any WinXP machine in the LAN. But I can ping myself (FreeBSD) locally. When I run netstat -rn, It seems the network card is ok. When I run tcpdump, I didn't show any output. By the way, this network card is CNet PRO200. I was thinking it was not recognize or supported by the FreeBSD-4.8. When I checked FreeBSD-4.8's Hardware Compatibility Lit, I didn't see any CNet PRO200 but I saw a CNet/PRO which I suppose are just the same. So, I recompiled my Kernel again just in case FreeBSD didn't recognize this newly installed Cnet LAN card. But, nothing changed after Kernel recompilation. (But I did not change any option in the Generic kernel; just re-compiled it). The output when I ping WinXP3: ping: sendto: Host is down. It's not true coz Im typing this email right in the WinXP3 machine. I cannot also ping FreeBSD's IP add from the WinXP internet sharing server. The dmesg shows the following: pci0 unknown card (vendor=0x1106 dev=0x3059) at 17.5 irq 5. By the way, this machine where FreeBSD is installed also has WinXP which works fine when in Windows. So Im sure my LAN card is really ok. It's only a problem of FreeBSD. What should I do? I don't want to make FreeBSD machine as my Internet sharing server as of now (although its the best option). Im testing/running a Unix program that needs to be connected to the Internet via Windows XP gateway. Please help me make my FreeBSD be part of my LAN -Edwin best regards, \___\__\___/__/ Edwin D. Viñas http://edwin.ontheweb.com \___\__\_/__/ Electronics and Communications Engineer \___\__\___/__/ Mobile: +639202612660 \___\__\_/__/E-mail: [EMAIL PROTECTED] PH \___\_/ The Brain is as vast as the Universe. - Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Problem on FreeBSD-4.8 : Cannot ping LAN hosts
On Thu, Sep 18, 2003 at 09:06:19AM -0700, Edwin D. Vinas wrote: Hi, I've stumbling with all the mailing lists about this problem and I hope somebody will give a kind advise. Here's my LAN setup: | | || | WinXP1 WinXP2 WinXP3 WinXP4 FreeBSD WinXP3 is my Internet Sharing Machine connected to my ISP. I can browse the web using all the WinXPs but I cannot access the web via FreeBSD. FreeBSD's IP address follows the 192.198.0.x format just like the other WinXPs. When I check the FreeBSD, i can see its IP address and Subnet Mask etc via ifconfig. I can even change the IP address+ Gateway (which is WinXP2's IP add) using ifconfig or /stand/sysinstall. I even manually edited rc.conf, and even changed the setting to DHCP etc etc etc. My diagnosis tells that I cannot ping any WinXP machine in the LAN. But I can ping myself (FreeBSD) locally. When I run netstat -rn, It seems the network card is ok. When I run tcpdump, I didn't show any output. By the way, this network card is CNet PRO200. I was thinking it was not recognize or supported by the FreeBSD-4.8. When I checked FreeBSD-4.8's Hardware Compatibility Lit, I didn't see any CNet PRO200 but I saw a CNet/PRO which I suppose are just the same. So, I recompiled my Kernel again just in case FreeBSD didn't recognize this newly installed Cnet LAN card. But, nothing changed after Kernel recompilation. (But I did not change any option in the Generic kernel; just re-compiled it). The output when I ping WinXP3: ping: sendto: Host is down. It's not true coz Im typing this email right in the WinXP3 machine. I cannot also ping FreeBSD's IP add from the WinXP internet sharing server. The dmesg shows the following: pci0 unknown card (vendor=0x1106 dev=0x3059) at 17.5 irq 5. By the way, this machine where FreeBSD is installed also has WinXP which works fine when in Windows. So Im sure my LAN card is really ok. It's only a problem of FreeBSD. What should I do? I don't want to make FreeBSD machine as my Internet sharing server as of now (although its the best option). Im testing/running a Unix program that needs to be connected to the Internet via Windows XP gateway. Please help me make my FreeBSD be part of my LAN -Edwin best regards, \___\__\___/__/ Edwin D. Vi?as http://edwin.ontheweb.com \___\__\_/__/ Electronics and Communications Engineer \___\__\___/__/ Mobile: +639202612660 \___\__\_/__/E-mail: [EMAIL PROTECTED] PH \___\_/ The Brain is as vast as the Universe. The output of dmesg and ifconfig would be helpful in diagnosing this. I suppose that's major PITA though considering you're LAN isn't working. At the very least, the first entry that comes up with ifconfig would be very helpful. Josh ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Problem on FreeBSD-4.8 : Cannot ping LAN hosts
hi josh, see dmesg, ifconfig and netstat below... hope you can help me now. -edwin IFCONFIG dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.6 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80::280:adff:fe00:591a%dc0 prefixlen 64 scopeid 0x1 ether 00:80:ad:00:59:1a media: Ethernet autoselect (100baseTX) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 faith0: flags=8002BROADCAST,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500 sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552 DN dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.6 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80::280:adff:fe00:591a%dc0 prefixlen 64 scopeid 0x1 ether 00:80:ad:00:59:1a media: Ethernet autoselect (100baseTX) status: active lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 faith0: flags=8002BROADCAST,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500 sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552 DMESG Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-RELEASE #0: Fri Feb 18 21:38:56 PHT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/CNETPRO Timecounter i8254 frequency 1193182 Hz CPU: AMD Duron(tm) processor (699.51-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x631 Stepping = 1 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! real memory = 268369920 (262080K bytes) avail memory = 255897600 (249900K bytes) Preloaded elf kernel kernel at 0xc051d000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 7 entries at 0xc00fdf00 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 agp0: VIA Generic host to PCI bridge mem 0xe800-0xebff at device 0.0 on pci0 pcib1: PCI to PCI bridge (vendor=1106 device=b099) at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: NVidia model 0110 graphics accelerator at 0.0 irq 10 dc0: Davicom DM9102A 10/100BaseTX port 0xd000-0xd0ff mem 0xef00-0xefff irq 11 at device 9.0 on pci0 dc0: Ethernet address: 00:80:ad:00:59:1a miibus0: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI to ISA bridge (vendor=1106 device=3074) at device 17.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 8233 ATA100 controller port 0xd400-0xd40f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: VIA 83C572 USB controller port 0xd800-0xd81f irq 11 at device 17.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xdc00-0xdc1f irq 11 at device 17.3 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: VIA 83C572 USB controller port 0xe000-0xe01f irq 11 at device 17.4 on pci0 usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: unknown card (vendor=0x1106, dev=0x3059) at 17.5 irq 5 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 ad0: 29325MB Maxtor 6E030L0 [59582/16/63] at ata0-master UDMA100 acd0: DVD-ROM DVD-ROM DVD-16X6S at ata0-slave PIO4 Mounting root from ufs:/dev/ad0s2a ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0;
network problem with connecting out side the lan
After I have had a lot of in/out bound traffic going through my NAT box, I begin having problems with any getting any thing in or out. This problem only seems to come up after I have been using p2p or listening to streaming music for awhile. I can easily ping any box on my LAN with out any problems. Some times it will last just a short while, others it will last several minutes. The setup looks a little like this... 192.168.0.1 natd/defualt fxp0: cable fxp1: LAN OS: FreeBSD 4.6.2-RELEASE 192.168.0.2 server/archive/whatever This box has a cheap realtek ethernet card in it... iirc a 8129. OS: 4.8-stable/current(forget which) 192.168.0.3 gfx box dc: OS 4.7-release 192.168.0.4 gaming box /me forgets what network card it has in it OS: win98 Then I have a Zonet 10/100 switch. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Network Problem with custom kernel
Hi, I'm new to freebsd. I'm using 4.6.2-RELEASE. After compiling a custom kernel I'm getting problem in the network. When I try to ping any machine I get message ping: sendto: No route to host I can't even ping the localhost . I guess my network interface is properly detected. ifconfig shows my network interface is xl0 I've allowed everything in the firewall on the very first rule. These are the options I've put in the kernel device miibus device xl options INET options INET6 options MROUTING options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_FORWARD options IPFIREWALL_VERBOSE_LIMIT=100 options IPFIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT options IPFILTER options IPFILTER_LOG options IPFILTER_DEFAULT_BLOCK options IPSTEALTH I guess I'm missing something. Also, how can I do make distclean (as in linux) if I want to recompile then kernel ? Thanks a lot. regards, Rohit Neupane ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Problem with custom kernel
On Tue, Jun 17, 2003 at 10:31:36AM +0545 or thereabouts, Rohit Neupane seemed to write: Hi, I'm new to freebsd. I'm using 4.6.2-RELEASE. After compiling a custom kernel I'm getting problem in the network. When I try to ping any machine I get message ping: sendto: No route to host I can't even ping the localhost . I guess my network interface is properly detected. ifconfig shows my network interface is xl0 I've allowed everything in the firewall on the very first rule. These are the options I've put in the kernel device miibus device xl options INET options INET6 options MROUTING options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_FORWARD options IPFIREWALL_VERBOSE_LIMIT=100 options IPFIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT options IPFILTER options IPFILTER_LOG options IPFILTER_DEFAULT_BLOCK ^ That's it, right there. options IPSTEALTH I guess I'm missing something. Also, how can I do make distclean (as in linux) if I want to recompile then kernel ? Thanks a lot. You've blocked all traffic by default. Blocking via firewall doesn't just block incoming packets; it blocks outbound ones too. You have three options: * Remove the IPFILTER_DEFAULT_BLOCK line * Run `ipf -D' * Set up an IPF firewall But really, why would you have both IPFIREWALL and IPFILTER in the kernel? You should only have one. -- Josh regards, Rohit Neupane ___ [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]
Help Troubleshooting Network problem
Hi all, I have a DSL connection and a Intel EtherPro 10/100 network card running FreeBSD 4.8 pre-release. I have noticed that sometimes when I'm downloading overnight, something like an iso image or something large that make ppp load seems to overflow and stop working. What happens is that all application that use a network connection lock up. Applications such as email web browser etc. I have to Kill the ppp pid and all application accessing it and restart them. I know this isn't the best description but can someone give me an idea on what to look at to try and trouble shoot this. I've never had this problem before with any release. I've even used 5.0 for awhile on this machine and had no such problem. Rod -- If you want to terrorize the world, you need the CIA. - Ralph McGhee, CIA Operative To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Network problem (stall after a few packets)
I have installed FreeBSD 4.6.2 on a system with a Realtek RTL8139 network card and I see a strange behaviour: I connect to the network, and get my IP with DHCP, but when I start a connection, e.g. I open lynx or a X browser, I download a few chilobytes and then the network stalls. I have tried 4.5 on the same machine and I did not experience this problem, I also use Windows every day on the same hardware and it works fine, so I am pretty sure that it is some comfiguration error I made. Oddly, I have less problems with www.freebsd.org than with java.sun.com or other sites. I installed Debian Linux 3.3r0 and I found the same problem. I am not sure if I enabled IPv6 (how can i tell?). Where could I start from for troubleshooting the problem? I would like to be able to reconfigure rl0 in different ways, but I do not know how (reinstalling everything is too stupid). I had experience with 4.3BSD on Sun, VAX and SVR4 from 1985 to 1992, so I think I can catch up easily once I have some pointers in hand. Thank you very much! Michele Costabile To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Network problem (stall after a few packets)
On Mon, Oct 07, 2002 at 10:27:02AM +0200, Michele Costabile wrote:
I have installed FreeBSD 4.6.2 on a system with a Realtek RTL8139
network card and I see a strange behaviour: I connect to the network,
and get my IP with DHCP, but when I start a connection, e.g. I open lynx
or a X browser, I download a few chilobytes and then the network stalls.
This sounds as if it might be a problem with autonegotiation of the
media settings between your NIC and your switch. (There's a very good
reason why those RealTek chipsets are universally despised amongst
people that develop ethernet drivers...)
Try forcing the card to use whatever settings are appropriate -- the
rl(4) has details of what media settings it understands. It's easy to
force those settings via ifconfig(8) if you aren't using DHCP --- you
might want to beg, borrow or steal yourself a static IP number at
least for a while so you can run some tests.
However, I think that the following snippet inserted into
/etc/dhclient.conf should override any media settings obtained from
the DHCP server or any autonegotiated settings. Untested, use at own
risk, slippery when wet. See dhclient.conf(5) for the gory details.
interface rl0 {
media media 100baseTX mediaopt full-duplex;
}
I am not sure if I enabled IPv6 (how can i tell?).
FreeBSD comes IPv6 capable --- generally to enable it for use on an
IPv6 network, you start by ifconfig'ing the interface with an inet6
address. If you aren't interested in IPv6, then you can simply
pretend it doesn't exist, and the machine will work perfectly well
with the IPv4 settings you give it.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: Network problem (stall after a few packets)
On Mon, Oct 07, 2002 at 10:27:02AM +0200, Michele Costabile wrote:
I have installed FreeBSD 4.6.2 on a system with a Realtek RTL8139
network card and I see a strange behaviour: I connect to the network,
and get my IP with DHCP, but when I start a connection, e.g. I open lynx
or a X browser, I download a few chilobytes and then the network stalls.
I have tried 4.5 on the same machine and I did not experience this
problem, I also use Windows every day on the same hardware and it works
fine, so I am pretty sure that it is some comfiguration error I made.
Oddly, I have less problems with www.freebsd.org than with java.sun.com
or other sites.
I installed Debian Linux 3.3r0 and I found the same problem.
I am not sure if I enabled IPv6 (how can i tell?).
Where could I start from for troubleshooting the problem?
I would like to be able to reconfigure rl0 in different ways, but I do
not know how (reinstalling everything is too stupid).
I had experience with 4.3BSD on Sun, VAX and SVR4 from 1985 to 1992, so
I think I can catch up easily once I have some pointers in hand.
Thank you very much!
See if it's an MTU issue. ifconfig rl0 mtu 1400. Half the internet
is broken :-(
Edwin
--
Edwin Groothuis |Personal website: http://www.MavEtJu.org
[EMAIL PROTECTED]|Weblog: http://www.mavetju.org/weblog/weblog.php
bash$ :(){ :|:};: | Interested in MUDs? http://www.FatalDimensions.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
