Networking problem running inside Virtualbox
I'm trying to track down a problem that seems to have been introduced after FreeBSD 8.0. I'm trying to install FreeBSD inside a virtualbox guest whose host is a Win7 64bit box running Vbox 4.0.2 PC-BSD based on FreeBSD 8.0 works fine. But FreeBSD 8.1 does not. Here is what does not work means in my case. Depending on the specific network adapter emulated in Vbox for FreeBSD I get the following: PC-Net II (works) PC-Net III (no dhcp address setup) Intel Pro/1000 MT Desktop (dhcp works, but network stack somehow does not. No network connectivity after dhcp assignment.) Intel Pro/1000 T Server (same as MT Desktop) Intel Pro/1000 MT Server (same as MT Desktop) I posted this question on the virutalbox mailing list and got a reply from someone else who is tracking the same issue I am, but neither of us have an answer. Because FreeBSD 8.0 works no matter what ethernet card is simulated and because PC-Net II still does work in 8.1, I suspect that FreeBSD is the culprit, but I can't prove it. All my other OSes work fine its just FreeBSD that gives me fits. I'm willing to make this problem report better, but I don't really understand how to debug this in the vm container. What information would be helpful? Rance ___ 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
interesting networking problem
[Domain name and IP addresses changed.] So there is a website, example.org, that I am trying to connect to. I can connect to this site (via http) *very* intermittently. If I run wget example.org, I get the page exactly, once, but if I run the same command immediately after, I get connection reset errors, e.g.: $ wget example.org --09:54:48-- http://example.org/ = `index.html' Resolving example.org... 192.168.1.5 Connecting to example.org|192.168.1.5|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] [ =] 19,83052.46K/s 09:54:48 (52.39 KB/s) - `index.html' saved [19830] $ wget example.org --09:54:49-- http://example.org/ = `index.html.1' Resolving example.org... 192.168.1.5 Connecting to example.org|192.168.1.5|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --09:54:53-- http://example.org/ (try: 2) = `index.html.1' Connecting to example.org|192.168.1.5|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. ^C If I wait couple of minutes and try again, the same thing happens... Normally I would write the whole thing off as a problem on their side, but I have access to other machines on different networks and in different cities and they both seem to have no problems accessing this page. In addition, I had a brief chat with someone on their side and they said they are not aware of any errors like this with anyone else who tries to connect to them. (They apparently block pings at the firewall -- I cannot ping them from any machine.) How can I debug this further? thanks, Thomas -- N.J. Thomas [EMAIL PROTECTED] Etiamsi occiderit me, in ipso sperabo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interesting networking problem
--- N.J. Thomas [EMAIL PROTECTED] wrote: [Domain name and IP addresses changed.] So there is a website, example.org, that I am trying to connect to. I can connect to this site (via http) *very* intermittently. If I run wget example.org, I get the page exactly, once, but if I run the same command immediately after, I get connection reset errors, e.g.: $ wget example.org --09:54:48-- http://example.org/ = `index.html' Resolving example.org... 192.168.1.5 Connecting to example.org|192.168.1.5|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] [ = ] 19,830 52.46K/s 09:54:48 (52.39 KB/s) - `index.html' saved [19830] $ wget example.org --09:54:49-- http://example.org/ = `index.html.1' Resolving example.org... 192.168.1.5 Connecting to example.org|192.168.1.5|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --09:54:53-- http://example.org/ (try: 2) = `index.html.1' Connecting to example.org|192.168.1.5|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. ^C If I wait couple of minutes and try again, the same thing happens... Normally I would write the whole thing off as a problem on their side, but I have access to other machines on different networks and in different cities and they both seem to have no problems accessing this page. In addition, I had a brief chat with someone on their side and they said they are not aware of any errors like this with anyone else who tries to connect to them. (They apparently block pings at the firewall -- I cannot ping them from any machine.) How can I debug this further? thanks, Thomas -- N.J. Thomas [EMAIL PROTECTED] Etiamsi occiderit me, in ipso sperabo Why don't you look at the http headers and see what's happening? __ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interesting networking problem
* Danial Thom [EMAIL PROTECTED] [2005-10-17 07:48:46 -0700]: I can connect to this site (via http) *very* intermittently. If I run wget example.org, I get the page exactly, once, but if I run the same command immediately after, I get connection reset errors, e.g.: Why don't you look at the http headers and see what's happening? Here they are. I'm not a web guru, so I don't really see anything out of the ordinary: $ wget -S example.org --12:07:03-- http://example.org/ = `index.html' Resolving example.org... 192.168.1.5 Connecting to example.org|192.168.1.5|:80... connected. HTTP request sent, awaiting response... HTTP/1.1 200 OK Date: Mon, 17 Oct 2005 16:09:55 GMT Server: Apache/2.0.54 (Win32) mod_ssl/2.0.54 OpenSSL/0.9.8 PHP/5.0.4 X-Powered-By: PHP/5.0.4 Connection: close Content-Type: text/html Length: unspecified [text/html] [ = ] 19,830 48.92K/s 12:07:04 (48.82 KB/s) - `index.html' saved [19830] $ wget -S example.org --12:07:07-- http://example.org/ = `index.html.1' Resolving example.org... 192.168.1.5 Connecting to example.org|192.168.1.5|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --12:07:08-- http://example.org/ (try: 2) = `index.html.1' Connecting to example.org|192.168.1.5|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. ^C Thomas -- N.J. Thomas [EMAIL PROTECTED] Etiamsi occiderit me, in ipso sperabo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: networking problem? maybe
If you have more than one computer available, try linking up a switch to your second Ethernet card and running a test between two machines that should not touch the gateway. What's your internal LAN speed when the gateway is not involved? That will tell you whether it's the gateway you need to look at. To explain better: ADSL | | (a) FreeBSD GW | (b) | Switch / \ Machine 1 Machine 2 Have Machine 1 talk to Machine 2. What's your speed? If it's significantly faster, then it's time to look at the gateway. If not, look at the switch. If it's the gateway, try reconfiguring your gateway so that the (b) ethernet card talks to the ADSL line and the (a) card talks to your LAN. Any change in speed? If so, it's probably the card or the config associated with it. If not, it's probably your routing configuration. Hope this gives you something to start from! -Original Message- From: neko hime [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 06, 2004 8:02 PM To: [EMAIL PROTECTED] Subject: networking problem? maybe Hi there, i have just installed freebsd 4.9 one of my machies. This box is configured to be a gateway/router. The install was a base install, and i recompiled with the IPFILTER options. Ive added the net.inet.ip.forwarding=1 to my /etc/sysctl.conf. When accessing the internet (via ADSL/PPPoE) on the gateway machine, my downloads are very fast, and im very happy. my problem is that when i connect any computer to this LAN, the speed drops dramatically. For example: From the gateway machine speed 90K/s. From Machine attached to gateway machine speed 10K/s. Im not very good with networking, so im not exactly sure how to troubleshoot this. May someone suggest something for me to check. I would like to keep my gateway with freebsd. I hope this wasn't too confusing. thank-you aya Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
networking problem? maybe
Hi there, i have just installed freebsd 4.9 one of my machies. This box is configured to be a gateway/router. The install was a base install, and i recompiled with the IPFILTER options. Ive added the net.inet.ip.forwarding=1 to my /etc/sysctl.conf. When accessing the internet (via ADSL/PPPoE) on the gateway machine, my downloads are very fast, and im very happy. my problem is that when i connect any computer to this LAN, the speed drops dramatically. For example: From the gateway machine speed 90K/s. From Machine attached to gateway machine speed 10K/s. Im not very good with networking, so im not exactly sure how to troubleshoot this. May someone suggest something for me to check. I would like to keep my gateway with freebsd. I hope this wasn't too confusing. thank-you aya Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 5.1 - WinXP Networking Problem UPDATE #2
-Original Message- From: freebsder [mailto:[EMAIL PROTECTED] Sent: Sunday, July 18, 2004 10:16 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: FreeBSD 5.1 - WinXP Networking Problem UPDATE #2 Hi Mark, I put in: natd_flags=-dynamic But I could not get it up and running. Btw, previously, what I've been doing to get the machine on line was typing in: # ipfw add 100 allow tcp from any to any via any 00100 allow tcp from any to any # ipfw add 100 allow ip from any to any via any 00100 allow ip from any to any I'm doing this because this allows me to surf the web and download my Email respectively. So when I do an ipfw, I get: # ipfw -a list 00100 308 68064 allow tcp from any to any 00100 38 3187 allow ip from any to any 65535 337 23993 deny ip from any to any Now, after I made the change you suggested and rebooted, I got: # ipfw -a list 00050 276 17396 divert 8668 ip from any to any via tun0 00100 134 14156 allow ip from any to any via lo0 00200 0 0 deny ip from any to 127.0.0.0/8 00300 0 0 deny ip from 127.0.0.0/8 to any 65000 0 0 allow ip from any to any 65535 0 0 deny ip from any to any Then I tried pinging out from my Win XP box to no avail. I even added: # ipfw add 100 allow tcp from any to any via any 00100 allow tcp from any to any # ipfw add 100 allow ip from any to any via any 00100 allow ip from any to any to get: 00050 286 17938 divert 8668 ip from any to any via tun0 00100 134 14156 allow ip from any to any via lo0 00100 0 0 allow tcp from any to any 00100 0 0 allow ip from any to any 00200 0 0 deny ip from any to 127.0.0.0/8 00300 0 0 deny ip from 127.0.0.0/8 to any 65000 0 0 allow ip from any to any 65535 0 0 deny ip from any to any but still no dice! I'm thinking I should probably Delete the following two lines from above: 00200 0 0 deny ip from any to 127.0.0.0/8 00300 0 0 deny ip from 127.0.0.0/8 to any and see what happends. I will try this out now, but if you have any other suggestions, prey tell. as always ... thankyou. Your Message:: Jumping in late, natd_enable=YES # forward from inside natd_interface=tun0 # this being the connection to outside world natd_flags=-dynamic # because the ip addy may change I don't know what your trying to do here?? natd_flags=redirect_port tcp 192.168.1.1:80 80 I would remove this until you get everything else working. This all looks fine to me. Is your winxp gateway set correctly? It should be the internal IP of your FreeBSd box. dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.1 - WinXP Networking Problem UPDATE #2
Hi Chuck,
Thanks for the suggestions.
First off - there was actually a typo in the line:
firewall_script=/etc/rc/firewall
I changed it to:
firewall_script=/etc/rc.firewall
However, it made no difference to the WinXP box
ability to connect.
Next I tried commenting out that line altogether but
it still did not work(!) It would not go online.
I then checked out rc.firewall asper you suggestion
and looked under OPEN ... This is what I found:::
# If you just configured ipfw in the kernel as a tool
to solve network
# problems or you just want to disallow some
particular kinds of traffic
# then you will want to change the default policy to
open. You can also
# do this as your only action by setting the
firewall_type to ``open''.
#
#${fwcmd} add 65000 pass all from any to any
# Prototype setups.
#
case ${firewall_type} in
[Oo][Pp][Ee][Nn])
setup_loopback
${fwcmd} add 65000 pass all from any to any
;;
[...]
Do you see a problem in this set-up?
I am considering setting it up in SIMPLE mode but I
want to be able to run the machine in OPEN mode before
I get too fancy with security and firewalls ... you
know?
Thanks again for you help ... please advise.
freebsder wrote:
This is what I get:
# ipfw -a list
00100 49820 12066079 allow ip from any to any
00100 00 allow tcp from any to any
65535 2 96 deny ip from any to any
The Second and Third lines don't seem right.. What
do
I need to do correct the problem here.
The line here:
firewall_script=/etc/rc/firewall
...tells IPFW to use a config file that doesn't
contain enough useful
rules.
Comment out that line, and examine /etc/rc.firewall
instead, and
reboot. Then
take a look at the rules being loaded by the OPEN
firewall type, which
should
include a divert rule...
--
-Chuck
__
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!
http://advision.webevents.yahoo.com/yahoo/votelifeengine/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1 - WinXP Networking Problem UPDATE #2
Hi Mark, I put in: natd_flags=-dynamic But I could not get it up and running. Btw, previously, what I've been doing to get the machine on line was typing in: # ipfw add 100 allow tcp from any to any via any 00100 allow tcp from any to any # ipfw add 100 allow ip from any to any via any 00100 allow ip from any to any I'm doing this because this allows me to surf the web and download my Email respectively. So when I do an ipfw, I get: # ipfw -a list 00100 308 68064 allow tcp from any to any 00100 38 3187 allow ip from any to any 65535 337 23993 deny ip from any to any Now, after I made the change you suggested and rebooted, I got: # ipfw -a list 00050 276 17396 divert 8668 ip from any to any via tun0 00100 134 14156 allow ip from any to any via lo0 00200 0 0 deny ip from any to 127.0.0.0/8 00300 0 0 deny ip from 127.0.0.0/8 to any 65000 0 0 allow ip from any to any 65535 0 0 deny ip from any to any Then I tried pinging out from my Win XP box to no avail. I even added: # ipfw add 100 allow tcp from any to any via any 00100 allow tcp from any to any # ipfw add 100 allow ip from any to any via any 00100 allow ip from any to any to get: 00050 286 17938 divert 8668 ip from any to any via tun0 00100 134 14156 allow ip from any to any via lo0 00100 0 0 allow tcp from any to any 00100 0 0 allow ip from any to any 00200 0 0 deny ip from any to 127.0.0.0/8 00300 0 0 deny ip from 127.0.0.0/8 to any 65000 0 0 allow ip from any to any 65535 0 0 deny ip from any to any but still no dice! I'm thinking I should probably Delete the following two lines from above: 00200 0 0 deny ip from any to 127.0.0.0/8 00300 0 0 deny ip from 127.0.0.0/8 to any and see what happends. I will try this out now, but if you have any other suggestions, prey tell. as always ... thankyou. Your Message:: Jumping in late, natd_enable=YES # forward from inside natd_interface=tun0 # this being the connection to outside world natd_flags=-dynamic # because the ip addy may change I don't know what your trying to do here?? natd_flags=redirect_port tcp 192.168.1.1:80 80 I would remove this until you get everything else working. Hi Bill, __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.1 - WinXP Networking Problem UPDATE #2
OK - I have taken everyone's advice and made some changes to my rc.conf. Things have improved ... All my computers can ping each other! BUT I can only connect to the internet from the FreeBSD server. All requests made by the WinXP machines go unanswered!! Yet when I ping from them, they can connect to any computer on the network BUT CANNOT ping OUTSIDE the network nor fetch any information outside this network. Any ideas why my FreeBSD machine is not routing these requests and putting up a road block? RC.CONF font8x14=NO font8x16=swiss-8x16 font8x8=swiss-8x8 inetd_enable=YES linux_enable=YES moused_enable=YES moused_port=/dev/psm0 moused_type=auto nfs_client_enable=YES nfs_server_enable=YES rpcbind_enable=YES saver=rain scrnmap=NO usbd_enable=YES ifconfig_vr0=DHCP ifconfig_ed0=DHCP ##initialise NIC network_interfaces=vr0 ed0 lo0 tun0 ifconfig tun0 #ifconfig vr0= media 10baseT/UTP up #ifconfig_ed0=inet 192.168.0.3 netmask 255.255.0.0 #Changes as suggested: ifconfig_ed0=inet 192.168.1.1/24 ifconfig_vr0=inet 192.168.0.1/24 media 10baseT/UTP up #ifconfig_vr0=inet 192.168.0.1 netmask 255.255.0.0 hostname=my.server.com ##User ppp configuration ppp_enable=YES ppp_mode=ddial ppp_nat=NO ppp_profile=bellnet #ppp_user=root ## Firewall gateway_enable=YES firewall_enable=YES firewall_type=OPEN #firewall_quiet=NO firewall_script=/etc/rc/firewall natd_enable=YES natd_interface=vr0 natd_flags=redirect_port tcp 192.168.1.1:80 80 rpc_statd_enable=YES tcp_extensions=YES ## Mail sendmail_enable=YES __ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1 - WinXP Networking Problem UPDATE #2
freebsder wrote: Any ideas why my FreeBSD machine is not routing these requests and putting up a road block? [ ... ] firewall_type=OPEN #firewall_quiet=NO firewall_script=/etc/rc/firewall natd_enable=YES There's likely to be a problem with /etc/rc/firewall, assuming that even exists. Does ipfw -a list show a divert rule to natd? -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1 - WinXP Networking Problem UPDATE #2
Hi Chuck, This is what I get: # ipfw -a list 00100 49820 12066079 allow ip from any to any 00100 00 allow tcp from any to any 65535 2 96 deny ip from any to any The Second and Third lines don't seem right.. What do I need to do correct the problem here. The Firewall Type is set to OPEN - doesn't that mean that it would not really matter how the firewall issetup. (btw, please excuse my overt ignorance.) I had it set to SIMPLE before and made some changes to the firewall file but it was not working so I just set it at OPEN and was able to access the internet. Although now this may pose a problem with this network. Please advise. I can send you a copy of my existing firewall file if needed ... Thanks as always freebsder wrote: Any ideas why my FreeBSD machine is not routing these requests and putting up a road block? [ ... ] firewall_type=OPEN #firewall_quiet=NO firewall_script=/etc/rc/firewall natd_enable=YES There's likely to be a problem with /etc/rc/firewall, assuming that even exists. Does ipfw -a list show a divert rule to natd? -- -Chuck __ Do you Yahoo!? Vote for the stars of Yahoo!'s next ad campaign! http://advision.webevents.yahoo.com/yahoo/votelifeengine/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1 - WinXP Networking Problem UPDATE #2
freebsder [EMAIL PROTECTED] wrote: All my computers can ping each other! BUT I can only connect to the internet from the FreeBSD server. All requests made by the WinXP machines go unanswered!! Yet when I ping from them, they can connect to any computer on the network BUT CANNOT ping OUTSIDE the network nor fetch any information outside this network. Any ideas why my FreeBSD machine is not routing these requests and putting up a road block? RC.CONF font8x14=NO font8x16=swiss-8x16 font8x8=swiss-8x8 inetd_enable=YES linux_enable=YES moused_enable=YES moused_port=/dev/psm0 moused_type=auto nfs_client_enable=YES nfs_server_enable=YES rpcbind_enable=YES saver=rain scrnmap=NO usbd_enable=YES ifconfig_vr0=DHCP ifconfig_ed0=DHCP ##initialise NIC network_interfaces=vr0 ed0 lo0 tun0 ifconfig tun0 #ifconfig vr0= media 10baseT/UTP up #ifconfig_ed0=inet 192.168.0.3 netmask 255.255.0.0 #Changes as suggested: ifconfig_ed0=inet 192.168.1.1/24 ifconfig_vr0=inet 192.168.0.1/24 media 10baseT/UTP up #ifconfig_vr0=inet 192.168.0.1 netmask 255.255.0.0 hostname=my.server.com ##User ppp configuration ppp_enable=YES ppp_mode=ddial ppp_nat=NO ppp_profile=bellnet #ppp_user=root ## Firewall gateway_enable=YES firewall_enable=YES firewall_type=OPEN #firewall_quiet=NO firewall_script=/etc/rc/firewall natd_enable=YES natd_interface=vr0 I believe you'll want: natd_interface=ppp0 or is it tun0? I don't remember (long time since I've used ppp) but the upshot is that whatever interface ppp creates when it dials, that's what you want natd_interface set to. natd_flags=redirect_port tcp 192.168.1.1:80 80 rpc_statd_enable=YES tcp_extensions=YES ## Mail sendmail_enable=YES -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1 - WinXP Networking Problem UPDATE #2
On Fri, 16 Jul 2004, freebsder wrote: Hi Chuck, This is what I get: # ipfw -a list 00100 49820 12066079 allow ip from any to any 00100 00 allow tcp from any to any 65535 2 96 deny ip from any to any The Second and Third lines don't seem right.. What do I need to do correct the problem here. First, you need to stop top-posting, which makes it difficult to reply. If you carefully read Chuck's response to you: There's likely to be a problem with /etc/rc/firewall, He's trying to tell you that should be /etc/rc.firewall (note the dot). -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]
Re: FreeBSD 5.1 - WinXP Networking Problem UPDATE #2
Hi Bill, The interface creates tun0 when it dials but I tried both tun0 and ppp0 and neither seemed to do the trick. Any other trouble shooting thoughts or ideas? Nav new RC.CONF : ## Firewall [...] natd_interface=tun0 #natd_interface=ppp0 #natd_interface=vr0 natd_flags=redirect_port tcp 192.168.1.1:80 80 rpc_statd_enable=YES tcp_extensions=YES ## Mail sendmail_enable=YES IFCONFIG : #ifconfig ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::280:c8ff:fede:c937%ed0 prefixlen 64 scopeid 0x1 ether 00:80:c8:de:c9:37 vr0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20e:a6ff:fe9c:c81d%vr0 prefixlen 64 scopeid 0x2 inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255 ether 00:0e:a6:9c:c8:1d media: Ethernet 10baseT/UTP 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 0x4 inet 127.0.0.1 netmask 0xff00 tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1492 inet 6X.7X.5X.23X -- 6X.23X.25X.12X netmask 0x Opened by PID 215 ORIGINAL MESSAGE Subject: Re: FreeBSD 5.1 - WinXP Networking Problem UPDATE #2 freebsder [EMAIL PROTECTED] wrote: All my computers can ping each other! BUT I can only connect to the internet from the FreeBSD server. All requests made by the WinXP machines go unanswered!! Yet when I ping from them, they can connect to any computer on the network BUT CANNOT ping OUTSIDE the network nor fetch any information outside this network. Any ideas why my FreeBSD machine is not routing these requests and putting up a road block? RC.CONF font8x14=NO font8x16=swiss-8x16 font8x8=swiss-8x8 inetd_enable=YES linux_enable=YES moused_enable=YES moused_port=/dev/psm0 moused_type=auto nfs_client_enable=YES nfs_server_enable=YES rpcbind_enable=YES saver=rain scrnmap=NO usbd_enable=YES ifconfig_vr0=DHCP ifconfig_ed0=DHCP ##initialise NIC network_interfaces=vr0 ed0 lo0 tun0 ifconfig tun0 #ifconfig vr0= media 10baseT/UTP up #ifconfig_ed0=inet 192.168.0.3 netmask 255.255.0.0 #Changes as suggested: ifconfig_ed0=inet 192.168.1.1/24 ifconfig_vr0=inet 192.168.0.1/24 media 10baseT/UTP up #ifconfig_vr0=inet 192.168.0.1 netmask 255.255.0.0 hostname=my.server.com ##User ppp configuration ppp_enable=YES ppp_mode=ddial ppp_nat=NO ppp_profile=bellnet #ppp_user=root ## Firewall gateway_enable=YES firewall_enable=YES firewall_type=OPEN #firewall_quiet=NO firewall_script=/etc/rc/firewall natd_enable=YES natd_interface=vr0 I believe you'll want: natd_interface=ppp0 or is it tun0? I don't remember (long time since I've used ppp) but the upshot is that whatever interface ppp creates when it dials, that's what you want natd_interface set to. natd_flags=redirect_port tcp 192.168.1.1:80 80 rpc_statd_enable=YES tcp_extensions=YES ## Mail sendmail_enable=YES __ Do you Yahoo!? Vote for the stars of Yahoo!'s next ad campaign! http://advision.webevents.yahoo.com/yahoo/votelifeengine/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1 - WinXP Networking Problem UPDATE #2
On Fri, Jul 16, 2004 at 06:37:08PM -0700, freebsder wrote: Jumping in late, natd_enable=YES # forward from inside natd_interface=tun0 # this being the connection to outside world natd_flags=-dynamic # because the ip addy may change I don't know what your trying to do here?? natd_flags=redirect_port tcp 192.168.1.1:80 80 I would remove this until you get everything else working. Hi Bill, The interface creates tun0 when it dials but I tried both tun0 and ppp0 and neither seemed to do the trick. Any other trouble shooting thoughts or ideas? Nav new RC.CONF : ## Firewall [...] natd_interface=tun0 #natd_interface=ppp0 #natd_interface=vr0 natd_flags=redirect_port tcp 192.168.1.1:80 80 rpc_statd_enable=YES tcp_extensions=YES ## Mail sendmail_enable=YES IFCONFIG : #ifconfig ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::280:c8ff:fede:c937%ed0 prefixlen 64 scopeid 0x1 ether 00:80:c8:de:c9:37 vr0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20e:a6ff:fe9c:c81d%vr0 prefixlen 64 scopeid 0x2 inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.255 ether 00:0e:a6:9c:c8:1d media: Ethernet 10baseT/UTP 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 0x4 inet 127.0.0.1 netmask 0xff00 tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1492 inet 6X.7X.5X.23X -- 6X.23X.25X.12X netmask 0x Opened by PID 215 ORIGINAL MESSAGE Subject: Re: FreeBSD 5.1 - WinXP Networking Problem UPDATE #2 freebsder [EMAIL PROTECTED] wrote: All my computers can ping each other! BUT I can only connect to the internet from the FreeBSD server. All requests made by the WinXP machines go unanswered!! Yet when I ping from them, they can connect to any computer on the network BUT CANNOT ping OUTSIDE the network nor fetch any information outside this network. Any ideas why my FreeBSD machine is not routing these requests and putting up a road block? RC.CONF font8x14=NO font8x16=swiss-8x16 font8x8=swiss-8x8 inetd_enable=YES linux_enable=YES moused_enable=YES moused_port=/dev/psm0 moused_type=auto nfs_client_enable=YES nfs_server_enable=YES rpcbind_enable=YES saver=rain scrnmap=NO usbd_enable=YES ifconfig_vr0=DHCP ifconfig_ed0=DHCP ##initialise NIC network_interfaces=vr0 ed0 lo0 tun0 ifconfig tun0 #ifconfig vr0= media 10baseT/UTP up #ifconfig_ed0=inet 192.168.0.3 netmask 255.255.0.0 #Changes as suggested: ifconfig_ed0=inet 192.168.1.1/24 ifconfig_vr0=inet 192.168.0.1/24 media 10baseT/UTP up #ifconfig_vr0=inet 192.168.0.1 netmask 255.255.0.0 hostname=my.server.com ##User ppp configuration ppp_enable=YES ppp_mode=ddial ppp_nat=NO ppp_profile=bellnet #ppp_user=root ## Firewall gateway_enable=YES firewall_enable=YES firewall_type=OPEN #firewall_quiet=NO firewall_script=/etc/rc/firewall natd_enable=YES natd_interface=vr0 I believe you'll want: natd_interface=ppp0 or is it tun0? I don't remember (long time since I've used ppp) but the upshot is that whatever interface ppp creates when it dials, that's what you want natd_interface set to. natd_flags=redirect_port tcp 192.168.1.1:80 80 rpc_statd_enable=YES tcp_extensions=YES ## Mail sendmail_enable=YES __ Do you Yahoo!? Vote for the stars of Yahoo!'s next ad campaign! http://advision.webevents.yahoo.com/yahoo/votelifeengine/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- -- ** The information contained in this communication is confidential, private, proprietary, or otherwise privileged and is intended only for the use of the addressee. Unauthorized use, disclosure, distribution or copying is strictly prohibited and may be unlawful. If you have received this communication in error, please notify the sender immediately. ** == ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org
FreeBSD 5.1 - WinXP Networking Problem UPDATE
Thanks to everyone for their patience and help ... you know who you are. I have gotten rid of the vr0 config line My RC.CONF file now looks like this: [...] ##initialise NIC network_interfaces=vr0 ed0 lo0 tun0 ifconfig tun0 ifconfig vr0= media 10baseT/UTP up ifconfig_ed0=inet 192.168.0.1 netmask 255.255.0.0 #ifconfig_vr0=inet 192.168.0.1 netmask 255.255.0.0 hostname=thor.nsvm.com ##User ppp configuration ppp_enable=YES ppp_mode=ddial ppp_nat=NO ppp_profile=bellnet #ppp_user=root ## Firewall gateway_enable=YES firewall_enable=YES firewall_type=OPEN #firewall_quiet=NO firewall_script=/etc/rc/firewall natd_enable=YES natd_interface=vr0 natd_flags=redirect_port tcp 192.168.0.3:80 80 rpc_statd_enable=YES tcp_extensions=YES ## Mail sendmail_enable=YES __ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.1 - WinXP Networking Problem UPDATE
Hi Everyone ... thanks for your help thus far. I've
made some changes below. [I have Not made all the
changes that you've kindly suggested but enough that I
am able to ping back and forth ... if I have ignored
your suggestion and you still see a gapping error,
please feel free to reinterate, I won't hold it again
you!]
OK, the changes ...
-I got rid of the ifconfig_vr0
-I set ifconfig_ed0 to 192.168.0.1 (where as _vr0 was
initially set as the gateway)
- I tried pinging from Freebsd to 192.168.0.4 the
WinXP #2 machine. and got through!
- I tried pinging from the WindXP #2 to itself at
192.168.0.4 andit got through.
- I tried pinging from the WindXP #2 to ed0 at
192.168.0.1 andit got through!
BUT I still cannot get the WIN XP webbrowser to read
the internet.
What is wrong?
I think that the
natd_flags=redirect_port tcp 192.168.0.3:80 80
should be:
natd_flags=redirect_port tcp 192.168.0.1:80 80
I will try changing this and see what happends
I have include the revised RC.CONF below:
[...]
font8x14=NO
font8x16=swiss-8x16
font8x8=swiss-8x8
inetd_enable=YES
linux_enable=YES
moused_enable=YES
moused_port=/dev/psm0
moused_type=auto
nfs_client_enable=YES
#nfs_server_enable=YES
rpcbind_enable=YES
saver=rain
scrnmap=NO
usbd_enable=YES
ifconfig_vr0=DHCP
##initialise NIC
network_interfaces=vr0 ed0 lo0 tun0
ifconfig tun0
ifconfig vr0= media 10baseT/UTP up
ifconfig_ed0=inet 192.168.0.1 netmask 255.255.0.0
#ifconfig_vr0=inet 192.168.0.1 netmask 255.255.0.0
hostname=myserver
##User ppp configuration
ppp_enable=YES
ppp_mode=ddial
ppp_nat=NO
ppp_profile=bellnet
#ppp_user=root
## Firewall
gateway_enable=YES
firewall_enable=YES
firewall_type=OPEN
#firewall_quiet=NO
firewall_script=/etc/rc/firewall
natd_enable=YES
natd_interface=vr0
natd_flags=redirect_port tcp 192.168.0.3:80 80
rpc_statd_enable=YES
tcp_extensions=YES
## Mail
sendmail_enable=YES
This is what my ifconfig looks like:
ed0:
flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu
1500
inet 192.168.0.1 netmask 0x broadcast
192.168.255.255
inet6 fe80::280:c8ff:fede:c937%ed0 prefixlen
64 scopeid 0x1
ether 00:80:c8:de:c9:37
vr0:
flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu
1500
inet6 fe80::20e:a6ff:fe9c:c81d%vr0 prefixlen
64 scopeid 0x2
inet 0.0.0.0 netmask 0xff00 broadcast
255.255.255.255
ether 00:0e:a6:9c:c8:1d
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 0x4
inet 127.0.0.1 netmask 0xff00
tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu
1492
inet 6X.9X.11X.3X -- 6X.23X.25X.12X netmask
0x
Opened by PID 222
Also, a small problem --- I have a webserver running
on the Freebsd box but everytime I reboot, I get a new
IP address(from above: 6X.9X.11X.3X). The fixed IP
address always seems to be: 6X.23X.25X.12X. However,
I have my domain name set to redirect towardsthe
dynamic address so everytime I reboot, I have to tell
the DNS server that holds my domain name my new IP
address. Is there a way to configure it so that I
don't have to continuously change the IP address on
the DNS?
Should I just get rid of the line:
ifconfig_vr0=DHCP
and set the DNS to 6X.23X.25X.12X? Would that do the
trick? Or should I get rid of ifconfig_ed0=DHCP?
Thanks again
MY original Post
I have a Freebsd 5.1 box connected to the internet.
It works. But I am now trying to network two other
Win XP machines as per the following network
hierarchy:
Setup
ISP- DSL Modem - FreeBSD box :
1) vr0 192.168.0.1 [Gateway machine address]
2) ed0 192.168.0.3 [Internal Network address]
connects to:-
4- port HUB -
1)WinXP machine #1 192.168.0.2
2)Freebsd Box 192.168.0.3
3)WinXP machine #2 192.168.0.4
Problem:
I cannot communicate to the Internet from WinXP #2
(Have not tried to config WinXP #1 yet).
Browser Config
IE Brower Settings for WinXP #2 {ToolsInternet
OptionsConnections)
-I set the browser so that it never dials a connection
because it is suppose to be networked right?
- in the LAN Settings option, I set the Proxyserver
option with the address of the gateway of 192.168.0.1
with Port 80
Dialouge
From Freebsd Machine
# ping 192.168.0.4
PING 192.168.0.4 (192.168.0.4): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
-at one point I was able to ping the freebsd machine
from WinXP #2 but then for some reason, I made a
change and cannot ping anymore...
RC.CONF
My rc.conf file looks like this:
RE: FreeBSD 5.1 - WinXP Networking Problem UPDATE
From: freebsder [mailto:[EMAIL PROTECTED] Hi Everyone ... thanks for your help thus far. I've made some changes below. [I have Not made all the changes that you've kindly suggested but enough that I am able to ping back and forth ... if I have ignored your suggestion and you still see a gapping error, please feel free to reinterate, I won't hold it again you!] ... I think that the natd_flags=redirect_port tcp 192.168.0.3:80 80 should be: natd_flags=redirect_port tcp 192.168.0.1:80 80 natd_flags=redirect_port tcp 192.168.1.1:80 80 ifconfig vr0= media 10baseT/UTP up ifconfig_ed0=inet 192.168.0.1 netmask 255.255.0.0 ifconfig_vr0=inet 192.168.0.1/24 media 10baseT/UTP up ifconfig_ed0=inet 192.168.1.1/24 You will then need to change the IP addresses of the two WinXP machines to use addresses starting with 192.168.1 (excluding .0, .1 and .255), a netmask of 255.255.255.0 and a gateway of 192.168.1.1. Thanks to Matthew Seaman for bringing to my attention that ifconfig now supports CIDR notation. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Networking problem! Watchdog -- Timeout
Hi all! Installing 5.2 on my new box with an integraded Intel PRO 1000 CT NIC. System detects it as em0 but I cant get it to work. I'm trying dhcp and I have added the line: ifconfig_em0=DHCP in rc.conf but I still get this problem. em0: Watchdog Timeout ---Resetting IF I disable ACPI it works perfectly so I think it's IRQ related or? dmesg.boot show the folowwing error messages: ACPI 1287 Method Execution Failed [_SB_PCI0.MDET] (Node 0xc29afb60) AE_AML_REGION_LIMIT ACPI 1287 Method Execution Failed [_SB_PCI0._CRS] (Node 0xc29afa60) AE_AML_REGION_LIMIT ACPI 0175 Method Execution Failed [_SB_PCI0._CRS] (Node 0xc29afa60) AE_AML_REGION_LIMIT cant fetch resource for _SB_PCI0 ACPI 1287 Method Execution Failed [_SB_PCI0.MDET] (Node 0xc29afb60) AE_AML_REGION_LIMIT ACPI 1287 Method Execution Failed [_SB_MEM_._CRS] (Node 0xc29af600) AE_AML_REGION_LIMIT ACPI 0175 Method Execution Failed [_SB_MEM_._CRS] (Node 0xc29af600) AE_AML_REGION_LIMIT cant fetch resource for _SB_.MEM_ Driver version is 1.7.19. I've tried at numerous forums but no answers =( Please help! I love FreeBSD but sometimes I realize why Win still exists =0) See ya! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem! Watchdog -- Timeout
Henrik Zagerholm wrote: Hi all! Installing 5.2 on my new box with an integraded Intel PRO 1000 CT NIC. System detects it as em0 but I cant get it to work. I'm trying dhcp and I have added the line: ifconfig_em0=DHCP in rc.conf but I still get this problem. em0: Watchdog Timeout ---Resetting IF I disable ACPI it works perfectly so I think it's IRQ related or? Please note that I am not associated with the Project while you read this. I think that this is a bug with the em driver on the 5.X series. You did note that it's a new technology release and not advertised to be suitable for everybody, right? IIRC, there have been issues with both em(4) and ACPI on the -HEAD (CURRENT, 5.X) code for a while. Good programmers are giving lots of the time and energy, coding for free to get it working, but some things are tricky. You might run without ACPI for a while, switch NICs until the problem is fixed, or run 4.9 or 4.10 [which is due out Real Soon Now(tm)] instead of 5.2 Kevin Kinsey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem! Watchdog -- Timeout
Kevin D. Kinsey, DaleCo, S.P. wrote: Henrik Zagerholm wrote: Hi all! Installing 5.2 on my new box with an integraded Intel PRO 1000 CT NIC. System detects it as em0 but I cant get it to work. I'm trying dhcp and I have added the line: ifconfig_em0=DHCP in rc.conf but I still get this problem. em0: Watchdog Timeout ---Resetting IF I disable ACPI it works perfectly so I think it's IRQ related or? Please note that I am not associated with the Project while you read this. I think that this is a bug with the em driver on the 5.X series. You did note that it's a new technology release and not advertised to be suitable for everybody, right? IIRC, there have been issues with both em(4) and ACPI on the -HEAD (CURRENT, 5.X) code for a while. Good programmers are giving lots of the time and energy, coding for free to get it working, but some things are tricky. You might run without ACPI for a while, switch NICs until the problem is fixed, or run 4.9 or 4.10 [which is due out Real Soon Now(tm)] instead of 5.2 Kevin Kinsey I guess you have a good point! =0) I just now another guy with the some NIC (Intel PRO 1000 CT) and it worked fine but it could be antoher device that is really messing up my system. What eactly do I miss with ACPI disabled? Have a good one Kevin! Sincerely, Henrik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Networking problem
Hi all! Installing 5.2 on my new box with an integraded Intel PRO 1000+ NIC. System detects it as em0 but I cant get it to work. I'm trying dhcp and I have added the line: ifconfig_em0=DHCP in rc.conf but I still get this problem. As far as I know there shouldnt be any problem with this NIC. My router works fine with my other bsd and win boxes... Suggestions? Take care! //Henrik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem
Hi! I do have the same problem with my Intel Gigabit onboard NIC. The system detects it, but it doesn't work. Do you also get watchdog timeouts?? I traced it down to a PCI interrupt problem. dmesg: pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.CSAB - AE_NOT_FOUND Booting without ACPI helps!! (but breaks other stuff :( ) Cheers, Ben On Sunday 18 April 2004 22:21, Henrik Zagerholm wrote: Hi all! Installing 5.2 on my new box with an integraded Intel PRO 1000+ NIC. System detects it as em0 but I cant get it to work. I'm trying dhcp and I have added the line: ifconfig_em0=DHCP in rc.conf but I still get this problem. As far as I know there shouldnt be any problem with this NIC. My router works fine with my other bsd and win boxes... Suggestions? Take care! //Henrik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem UPDATED
On Thu, 4 Mar 2004, Steve Ireland wrote: The two interfaces are on different subnets: 192.168.0.0/24 and 192.168.10.0/24. You need to either add a static route between them or change their netmasks to at least a /21. Huh? They _must_ be on different subnets. You can't route one subnet across multiple network interfaces. Besides, a router always knows how to route packets between its own directly-attached networks, no additional routes are necessary. The problem here is that a route needs to be added for 192.168.10.0/24 - 192.168.0.100 in the upstream router(s), since the upstream router(s) do not currently know to send any packets destined for 192.168.10.0/24 to 192.168.0.100 for delivery. The upstream router is currently sending these packets to its own default gateway, which is likely even further upstream. IP routers aren't mind-readers, you have to tell them exactly where to send packets, but usually that is very simple. Running a routing protocol (such as RIP) on both the FreeBSD box in question and the upstream router(s) would automatically add the same route for you, but that is unnecessary in such a simple network configuration. -- Chris Dillon - cdillon(at)wolves.k12.mo.us FreeBSD: The fastest, most open, and most stable OS on the planet - Available for IA32, IA64, AMD64, PC98, Alpha, and UltraSPARC architectures - PowerPC, ARM, MIPS, and S/390 under development - http://www.freebsd.org Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Networking problem
I have a friend who can not get his FreeBSD 5.2 server to act as a gateway, from the internal network we can ping the external network card, but no further. From the server we can ping the entire world. I had him bring it over and set up my server (FreeBSD 4.8R as the gateway) so I now have: ISPMy Server---his Server---laptop From the laptop I can ping as far as the external nic on his server. From his server I can ping the world. I have googled, looked at the mailing list, but can not find the problem :o( I have re installed the server, incase he goofed up, same problem, I have swapped the external network card, same problem. Netstat -rn shows the default gateway (as my server) In rc.conf it has gateway_enable=YES I am out of ideas Regards, Kat. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.593 / Virus Database: 376 - Release Date: 20/02/2004 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem
On Thu, 4 Mar 2004, Kathy Quinlan wrote: I have a friend who can not get his FreeBSD 5.2 server to act as a gateway, from the internal network we can ping the external network card, but no further. From the server we can ping the entire world. I had him bring it over and set up my server (FreeBSD 4.8R as the gateway) so I now have: ISPMy Server---his Server---laptop From the laptop I can ping as far as the external nic on his server. From his server I can ping the world. I have googled, looked at the mailing list, but can not find the problem :o( I have re installed the server, incase he goofed up, same problem, I have swapped the external network card, same problem. Netstat -rn shows the default gateway (as my server) In rc.conf it has gateway_enable=YES I am out of ideas What IP addresses are used within the internal network? If you use addresses like 10., 172.16.-172.31. or 192.168.1.-191.168.254., you should use natd instead of routed on the server connected to the world outside. Regards Konrad Heuer ([EMAIL PROTECTED]) ___ ___ GWDG / __/__ ___ / _ )/ __/ _ \ Am Fassberg / _// __/ -_) -_) _ |\ \/ // / 37077 Goettingen /_/ /_/ \__/\__//___// Germany ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Networking problem UPDATED
I have a friend who can not get his FreeBSD 5.2 server to act as a gateway, from the internal network we can ping the external network card, but no further. From the server we can ping the entire world. I had him bring it over and set up my server(FreeBSD 4.8R as the gateway) all my clients can use my FreeBSD server fine, so I do not think the problem is in it, so I now have: ISPMy Server---his Server---laptop My Server to ISP is a dynamic IP (ppp dialup) My server internal network is 192.168.0.1 His server to my server is connected to my servers hub and his server uses ip 192.168.0.100 His server to my laptop is connected with a cross over cable, his server is 192.168.10.1 My Laptop is 192.168.10.42 From the laptop I can ping as far as the external nic on his server (192.168.0.100). From his server I can ping the world. I have googled, looked at the mailing list, but can not find the problem :o( I have re installed the server, incase he goofed up, same problem, I have swapped the external network card, same problem. His Server rc.conf: defaultrouter=192.168.0.1 gateway_enable=YES hostname=osire.home.lan ifconfig_fxp0=inet 192.168.0.100 netmask 255.255.255.0 #external nic ifconfig_rl0=inet 192.168.10.1 netmask 255.255.255.0 #internal nic inetd_enable=YES saver=logo sshd_enable=YES osire# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.0.1UGS 00 fxp0 127.0.0.1 127.0.0.1 UH 0 49lo0 192.168.0 link#1 UC 00 fxp0 192.168.0.100:02:b3:99:46:d0 UHLW13 fxp0 1043 192.168.0.254 00:e0:29:9c:ea:72 UHLW0 165 fxp0 1039 192.168.10 link#2 UC 00rl0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%fxp0/64link#1UC fxp0 fe80::2a0:c9ff:fe8e:3980%fxp0 00:a0:c9:8e:39:80 UHL lo0 fe80::%rl0/64 link#2UC rl0 fe80::240:f4ff:fe3c:9deb%rl0 00:40:f4:3c:9d:eb UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#4UHL lo0 ff01::/32 ::1 U lo0 ff02::%fxp0/32link#1UC fxp0 ff02::%rl0/32 link#2UC rl0 ff02::%lo0/32 ::1 UC lo0 osire# There is no firewall or natd running on his server My Server rc.conf: Generated by Katinka 16-07-03 amd_enable=NO gateway_enable=YES hostname=webserver.kaqelectronics.dyndns.org ifconfig_fxp0=inet 192.168.0.1 netmask 255.255.255.0 ifconfig_rl0=media 10baseT/UTP up ipv6_enable=NO kern_securelevel_enable=NO portmap_enable=YES nfs_server_enable=YES mountd_flags=-r inetd_enable=YES nfs_reserved_port_only=YES saver=logo scrnmap=NO sendmail_enable=YES sshd_enable=YES tcp_extensions=YES usbd_enable=YES firewall_enable=YES firewall_type=OPEN named_enable=YES named_flags=/etc/namedb/named.conf sasl_saslauthd_enabled=YES ppp_enable=YES ppp_profile=dialup ppp_mode=ddial webserver# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default203.30.44.55 UGSc 1532442 tun0 127.0.0.1 127.0.0.1 UH 0 7361lo0 192.168.0 link#2 UC 50 fxp0 192.168.0.6link#2 UHLW1 4155 fxp0 192.168.0.10 00:e0:18:b0:53:00 UHLW2 165561 fxp0 944 192.168.0.100 00:a0:c9:8e:39:80 UHLW13 fxp0 845 192.168.0.254 00:e0:29:9c:ea:72 UHLW2 569747 fxp0 841 192.168.0.255 ff:ff:ff:ff:ff:ff UHLWb 2 2578 fxp0 203.30.44.55 202.89.160.14 UH 160 tun0 webserver# I am out of ideas Regards, Kat. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.593 / Virus Database: 376 - Release Date: 20/02/2004 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem UPDATED
- Original Message - From: Kathy Quinlan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, March 04, 2004 19:46 Subject: Networking problem UPDATED I have a friend who can not get his FreeBSD 5.2 server to act as a gateway, from the internal network we can ping the external network card, but no further. From the server we can ping the entire world. I had him bring it over and set up my server(FreeBSD 4.8R as the gateway) all my clients can use my FreeBSD server fine, so I do not think the problem is in it, so I now have: ISPMy Server---his Server---laptop My Server to ISP is a dynamic IP (ppp dialup) My server internal network is 192.168.0.1 His server to my server is connected to my servers hub and his server uses ip 192.168.0.100 His server to my laptop is connected with a cross over cable, his server is 192.168.10.1 My Laptop is 192.168.10.42 From the laptop I can ping as far as the external nic on his server (192.168.0.100). From his server I can ping the world. I have googled, looked at the mailing list, but can not find the problem :o( I have re installed the server, incase he goofed up, same problem, I have swapped the external network card, same problem. His Server rc.conf: defaultrouter=192.168.0.1 gateway_enable=YES hostname=osire.home.lan ifconfig_fxp0=inet 192.168.0.100 netmask 255.255.255.0 #external nic ifconfig_rl0=inet 192.168.10.1 netmask 255.255.255.0 #internal nic inetd_enable=YES saver=logo sshd_enable=YES osire# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.0.1UGS 00 fxp0 127.0.0.1 127.0.0.1 UH 0 49lo0 192.168.0 link#1 UC 00 fxp0 192.168.0.100:02:b3:99:46:d0 UHLW13 fxp0 1043 192.168.0.254 00:e0:29:9c:ea:72 UHLW0 165 fxp0 1039 192.168.10 link#2 UC 00rl0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%fxp0/64link#1UC fxp0 fe80::2a0:c9ff:fe8e:3980%fxp0 00:a0:c9:8e:39:80 UHL lo0 fe80::%rl0/64 link#2UC rl0 fe80::240:f4ff:fe3c:9deb%rl0 00:40:f4:3c:9d:eb UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#4UHL lo0 ff01::/32 ::1 U lo0 ff02::%fxp0/32link#1UC fxp0 ff02::%rl0/32 link#2UC rl0 ff02::%lo0/32 ::1 UC lo0 osire# There is no firewall or natd running on his server My Server rc.conf: Generated by Katinka 16-07-03 amd_enable=NO gateway_enable=YES hostname=webserver.kaqelectronics.dyndns.org ifconfig_fxp0=inet 192.168.0.1 netmask 255.255.255.0 ifconfig_rl0=media 10baseT/UTP up ipv6_enable=NO kern_securelevel_enable=NO portmap_enable=YES nfs_server_enable=YES mountd_flags=-r inetd_enable=YES nfs_reserved_port_only=YES saver=logo scrnmap=NO sendmail_enable=YES sshd_enable=YES tcp_extensions=YES usbd_enable=YES firewall_enable=YES firewall_type=OPEN named_enable=YES named_flags=/etc/namedb/named.conf sasl_saslauthd_enabled=YES ppp_enable=YES ppp_profile=dialup ppp_mode=ddial webserver# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default203.30.44.55 UGSc 1532442 tun0 127.0.0.1 127.0.0.1 UH 0 7361lo0 192.168.0 link#2 UC 50 fxp0 192.168.0.6link#2 UHLW1 4155 fxp0 192.168.0.10 00:e0:18:b0:53:00 UHLW2 165561 fxp0 944 192.168.0.100 00:a0:c9:8e:39:80 UHLW13 fxp0 845 192.168.0.254 00:e0:29:9c:ea:72 UHLW2 569747 fxp0 841 192.168.0.255 ff:ff:ff:ff:ff:ff UHLWb 2 2578 fxp0 203.30.44.55 202.89.160.14 UH 160 tun0 webserver# I am out of ideas Regards, Kat. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.593 / Virus Database: 376 - Release Date: 20/02/2004 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hello, The two interfaces are on different subnets: 192.168.0.0/24 and 192.168.10.0/24. You need to either add
Re: Networking problem UPDATED - correction
That should have been /20 not /21. Sorry, Steve - Original Message - From: Kathy Quinlan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, March 04, 2004 19:46 Subject: Networking problem UPDATED I have a friend who can not get his FreeBSD 5.2 server to act as a gateway, from the internal network we can ping the external network card, but no further. From the server we can ping the entire world. I had him bring it over and set up my server(FreeBSD 4.8R as the gateway) all my clients can use my FreeBSD server fine, so I do not think the problem is in it, so I now have: ISPMy Server---his Server---laptop My Server to ISP is a dynamic IP (ppp dialup) My server internal network is 192.168.0.1 His server to my server is connected to my servers hub and his server uses ip 192.168.0.100 His server to my laptop is connected with a cross over cable, his server is 192.168.10.1 My Laptop is 192.168.10.42 From the laptop I can ping as far as the external nic on his server (192.168.0.100). From his server I can ping the world. I have googled, looked at the mailing list, but can not find the problem :o( I have re installed the server, incase he goofed up, same problem, I have swapped the external network card, same problem. His Server rc.conf: defaultrouter=192.168.0.1 gateway_enable=YES hostname=osire.home.lan ifconfig_fxp0=inet 192.168.0.100 netmask 255.255.255.0 #external nic ifconfig_rl0=inet 192.168.10.1 netmask 255.255.255.0 #internal nic inetd_enable=YES saver=logo sshd_enable=YES osire# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.0.1UGS 00 fxp0 127.0.0.1 127.0.0.1 UH 0 49lo0 192.168.0 link#1 UC 00 fxp0 192.168.0.100:02:b3:99:46:d0 UHLW13 fxp0 1043 192.168.0.254 00:e0:29:9c:ea:72 UHLW0 165 fxp0 1039 192.168.10 link#2 UC 00rl0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%fxp0/64link#1UC fxp0 fe80::2a0:c9ff:fe8e:3980%fxp0 00:a0:c9:8e:39:80 UHL lo0 fe80::%rl0/64 link#2UC rl0 fe80::240:f4ff:fe3c:9deb%rl0 00:40:f4:3c:9d:eb UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#4UHL lo0 ff01::/32 ::1 U lo0 ff02::%fxp0/32link#1UC fxp0 ff02::%rl0/32 link#2UC rl0 ff02::%lo0/32 ::1 UC lo0 osire# There is no firewall or natd running on his server My Server rc.conf: Generated by Katinka 16-07-03 amd_enable=NO gateway_enable=YES hostname=webserver.kaqelectronics.dyndns.org ifconfig_fxp0=inet 192.168.0.1 netmask 255.255.255.0 ifconfig_rl0=media 10baseT/UTP up ipv6_enable=NO kern_securelevel_enable=NO portmap_enable=YES nfs_server_enable=YES mountd_flags=-r inetd_enable=YES nfs_reserved_port_only=YES saver=logo scrnmap=NO sendmail_enable=YES sshd_enable=YES tcp_extensions=YES usbd_enable=YES firewall_enable=YES firewall_type=OPEN named_enable=YES named_flags=/etc/namedb/named.conf sasl_saslauthd_enabled=YES ppp_enable=YES ppp_profile=dialup ppp_mode=ddial webserver# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default203.30.44.55 UGSc 1532442 tun0 127.0.0.1 127.0.0.1 UH 0 7361lo0 192.168.0 link#2 UC 50 fxp0 192.168.0.6link#2 UHLW1 4155 fxp0 192.168.0.10 00:e0:18:b0:53:00 UHLW2 165561 fxp0 944 192.168.0.100 00:a0:c9:8e:39:80 UHLW13 fxp0 845 192.168.0.254 00:e0:29:9c:ea:72 UHLW2 569747 fxp0 841 192.168.0.255 ff:ff:ff:ff:ff:ff UHLWb 2 2578 fxp0 203.30.44.55 202.89.160.14 UH 160 tun0 webserver# I am out of ideas Regards, Kat. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.593 / Virus Database: 376 - Release Date: 20/02/2004 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hello, The two interfaces are on different subnets: 192.168.0.0/24
Networking problem
Hi, I posted similar question some time ago but I guess I misstated the problem. I will be more careful this time. Here is my situation: Node A - LAN1 - Node B - LAN2 - Node C Node A: OS: Win2K IP Address (to LAN1): 129.197.23.232 Node B: OS: FreeBSD 4.6 IP address (to LAN1): 129.197.244.10 IP address (to LAN2): 10.77.1.1 Node C: OS: FreeBSD 4.6 IP address (to LAN2) 10.77.2.1 What I am trying to accomplish is to set up Node A and Node B (and not Node C) to have Node A think that it is directly connected to LAN2 with an IP Address 10.77.1.2 So if Node A needs to send a packet to Node C, some program on Node A will encapsulate the packed and send it to Node B. Some other program on Node B will get the encapsulated packet, recognize that it came from Node A and that it needs to go somewhere else on LAN2, open the capsule and forward the original packet to the appropriate destination. And if Node C needs to send a packet to 10.77.1.2, the router on LAN2 will force it to send the packet to Node B. The Node B should then forward the packet to Node A. I tried to accomplish this in many ways but was not able to get exactly what I was looking for. I would highly appreciate if someone could tell me which program I need to use. ANY help if highly appreciated. I am really stuck... Thank you in advance. Sincerely Artem ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Networking problem
On Thu, 19 Jun 2003, Tkachenko, Artem N wrote: Hi, I posted similar question some time ago but I guess I misstated the problem. I will be more careful this time. Here is my situation: Node A - LAN1 - Node B - LAN2 - Node C Why can't you just set a static route on both Node A and Node C pointing to Node B (each one using it's corresponding IP, Node A points to 129.197.244.10) and enable IP forwarding on Node B? Fer ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bizarre Networking Problem
On Thu, 20 Feb 2003 at 7:20pm Bill Moran wrote: Perhaps some output form 'netstat -rn' and 'ifconfig' might provoke some more useful answers. Well the problem is solved, but I am not happy about the solution as it makes absolutely no sense to me. xl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=3rxcsum,txcsum inet 192.246.38.10 netmask 0xff00 broadcast 255.255.255.0 inet 208.23.240.10 netmask 0xff00 broadcast 208.23.240.255 ether 00:04:75:b0:24:12 media: Ethernet autoselect (100baseTX full-duplex) status: active The above was the ifconfig when I had the problem. Notice the broadcast addresses. The commands that brought up the interface at boot are: /sbin/ifconfig xl0 192.246.38.10 netmask 255.255.255.0 /sbin/ifconfig xl0 alias 208.23.240.10 netmask 255.255.255.0 (note that the netmask really is not required as those IP's are from traditional class C, but I like to always be specific so I don't forget one when I'm working in 'A' or 'B' space.) So those commands give two different kinds of broadcast addresses and to my way of thinking, the second one (on the 208...) is correct. But if I alias the interface like so: ifconfig inet 208.23.240.10 netmask 0xff00 broadcast 255.255.255.0 The sluggishness on the 208 net goes away. I don't understand it, but it works. I don't like stuff this, it creeps me out. -- Joseph F. Noonan Rigaku/MSC Inc. [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Bizarre Networking Problem
- Original Message - From: Joseph Noonan [EMAIL PROTECTED] To: Bill Moran [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, February 21, 2003 6:07 PM Subject: Re: Bizarre Networking Problem The above was the ifconfig when I had the problem. Notice the broadcast addresses. The commands that brought up the interface at boot are: /sbin/ifconfig xl0 192.246.38.10 netmask 255.255.255.0 /sbin/ifconfig xl0 alias 208.23.240.10 netmask 255.255.255.0 Hmm, I thought aliases always needed to have netmask of 255.255.255.255. Has something changed? - Mark To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Bizarre Networking Problem
Joseph Noonan wrote: On Thu, 20 Feb 2003 at 7:20pm Bill Moran wrote: Perhaps some output form 'netstat -rn' and 'ifconfig' might provoke some more useful answers. Well the problem is solved, but I am not happy about the solution as it makes absolutely no sense to me. xl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=3rxcsum,txcsum inet 192.246.38.10 netmask 0xff00 broadcast 255.255.255.0 inet 208.23.240.10 netmask 0xff00 broadcast 208.23.240.255 ether 00:04:75:b0:24:12 media: Ethernet autoselect (100baseTX full-duplex) status: active The above was the ifconfig when I had the problem. Notice the broadcast addresses. The commands that brought up the interface at boot are: /sbin/ifconfig xl0 192.246.38.10 netmask 255.255.255.0 /sbin/ifconfig xl0 alias 208.23.240.10 netmask 255.255.255.0 (note that the netmask really is not required as those IP's are from traditional class C, but I like to always be specific so I don't forget one when I'm working in 'A' or 'B' space.) So those commands give two different kinds of broadcast addresses and to my way of thinking, the second one (on the 208...) is correct. But if I alias the interface like so: ifconfig inet 208.23.240.10 netmask 0xff00 broadcast 255.255.255.0 That doesn't look right. The broadcast address should be 208.23.240.255 for that IP and 192.246.38.255 for the other one. Can you try these broadcast addys and see if the problem is fixed there as well? The sluggishness on the 208 net goes away. I don't understand it, but it works. I don't like stuff this, it creeps me out. Can't argue with you. I don't see how what you did would fix anything. However, I'm not surprised that ifconfig doesn't guess the right action all the time. I wouldn't get upset if you have to specify the broadcast addy to be sure it's right. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Bizarre Networking Problem
Well the problem is solved, but I am not happy about the solution as it makes absolutely no sense to me. xl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=3rxcsum,txcsum inet 192.246.38.10 netmask 0xff00 broadcast 255.255.255.0 inet 208.23.240.10 netmask 0xff00 broadcast 208.23.240.255 ether 00:04:75:b0:24:12 media: Ethernet autoselect (100baseTX full-duplex) status: active Your nic is set autosense. While probably not the only culprit, if you can manage your 3com switch, hard set the port and your NIC to 100 full duplex. It may not solve the problem, but its one more variable eliminated. I was running a HP 4000M and all the machines set auto. I did a code upgrade on the switch and all of sudden performance went in the gutter because, for some reason, autosense broke. Once I hard set 100fd on everything, performance was once again stellar. The broadcast for 192.246.38.10 is wrong too. You shouldn't have to run in promiscous mode to solve this... Doing so is going to kill your CPU when traffic gets high. Brent To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Bizarre Networking Problem
On Fri, Feb 21, 2003 at 05:17:17PM +, Mark wrote: From: Joseph Noonan [EMAIL PROTECTED] The above was the ifconfig when I had the problem. Notice the broadcast addresses. The commands that brought up the interface at boot are: /sbin/ifconfig xl0 192.246.38.10 netmask 255.255.255.0 /sbin/ifconfig xl0 alias 208.23.240.10 netmask 255.255.255.0 Hmm, I thought aliases always needed to have netmask of 255.255.255.255. Has something changed? Nope. You only use a netmask of 255.255.255.255 when the alias address is the second or subsequent address from a given network. If the alias address is the first one from a distinct network, it should have the regular netmask. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey 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
Netmasks for aliases (was Re: Bizarre Networking Problem)
On Friday 21 February 2003 19:17, Mark wrote: /sbin/ifconfig xl0 192.246.38.10 netmask 255.255.255.0 /sbin/ifconfig xl0 alias 208.23.240.10 netmask 255.255.255.0 Hmm, I thought aliases always needed to have netmask of 255.255.255.255. Has something changed? - Mark Mark, Aliases on the same subnet should always be 255.255.255.255, this does not apply where they are on different subnets, however. Here is a good example, from the ifconfig output of a mail server I set up at an ISP in a nearby town. They used to use a private range, but have since added a public class C which has been broken up into smaller ranges for routing. The mail server, for legacy reasons, still has to serve people on the old IPs because those are still being used by machines in their office, and reconfiguring every office machine with new server IP addresses (they didn't have internal DNS then) would be wasting time. We didn't want to waste public IPs on beancounters, so we just left their machines as is. The host is also serving on the new IP, and acting as a POP server for several virtual domains, which have aliases. The 10.0.1.0/24 range (their office), and the 196.38.113.0/27 range (used for their server farm + virtual domains) are still the same physical network though. The output from ifconfig follows: %ifconfig dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 196.38.113.2 netmask 0xffe0 broadcast 196.38.113.31 inet6 fe80::a00:8ff:fe00:800%dc0 prefixlen 64 scopeid 0x1 inet 196.38.113.3 netmask 0x broadcast 196.38.113.3 inet 196.38.113.5 netmask 0x broadcast 196.38.113.5 inet 196.38.113.6 netmask 0x broadcast 196.38.113.6 inet 196.38.113.7 netmask 0x broadcast 196.38.113.7 inet 196.38.113.8 netmask 0x broadcast 196.38.113.8 inet 196.38.113.9 netmask 0x broadcast 196.38.113.9 inet 196.38.113.10 netmask 0x broadcast 196.38.113.10 inet 196.38.113.11 netmask 0x broadcast 196.38.113.11 inet 10.0.1.4 netmask 0xff00 broadcast 10.0.1.255 inet 10.0.1.5 netmask 0x broadcast 10.0.1.5 ether 08:00:08:00:08:00 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff00 Note how 196.38.113.2 (the machine's real address) has a netmask of 0xffe0, or 255.255.255.224, and the other addresses in this range (all of them aliases) have 0x, 255.255.255.255. Then look at 10.0.1.4, which is an alias too. It has a netmask of 0xff00, or 255.255.255.0. Now look at 10.0.1.5, an alias used for serving intranet web content to legacy machines. Again, a netmask of 0x. The reason for this is that 10.0.1.4, even though being an alias, is the first address the machine handles on that subnet. Just as 196.38.113.2 is the first address the machine has on the public subnet. Rule of thumb: First address on a subnet, alias or not, has the proper subnet netmask. Every other address on the subnet following that, has 0x, or 255.255.255.255. Will To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Willie Viljoen Freelance IT Consultant 214 Paul Kruger Avenue, Universitas Bloemfontein 9321 South Africa +27 51 522 15 60 +27 51 522 44 36 (after hours) +27 82 404 03 27 (mobile) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Netmasks for aliases (was Re: Bizarre Networking Problem)
- Original Message - From: Willie Viljoen [EMAIL PROTECTED] To: Mark [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, February 21, 2003 7:24 PM Subject: Netmasks for aliases (was Re: Bizarre Networking Problem) On Friday 21 February 2003 19:17, Mark wrote: /sbin/ifconfig xl0 192.246.38.10 netmask 255.255.255.0 /sbin/ifconfig xl0 alias 208.23.240.10 netmask 255.255.255.0 Hmm, I thought aliases always needed to have netmask of 255.255.255.255. Has something changed? - Mark Mark, Aliases on the same subnet should always be 255.255.255.255, this does not apply where they are on different subnets, however. Here is a good example, from the ifconfig output of a mail server I set up at an ISP in a nearby town. They used to use a private range, but have since added a public class C which has been broken up into smaller ranges for routing. The mail server, for legacy reasons, still has to serve people on the old IPs because those are still being used by machines in their office, and reconfiguring every office machine with new server IP addresses (they didn't have internal DNS then) would be wasting time. We didn't want to waste public IPs on beancounters, so we just left their machines as is. The host is also serving on the new IP, and acting as a POP server for several virtual domains, which have aliases. The 10.0.1.0/24 range (their office), and the 196.38.113.0/27 range (used for their server farm + virtual domains) are still the same physical network though. The output from ifconfig follows: %ifconfig dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 196.38.113.2 netmask 0xffe0 broadcast 196.38.113.31 inet6 fe80::a00:8ff:fe00:800%dc0 prefixlen 64 scopeid 0x1 inet 196.38.113.3 netmask 0x broadcast 196.38.113.3 inet 196.38.113.5 netmask 0x broadcast 196.38.113.5 inet 196.38.113.6 netmask 0x broadcast 196.38.113.6 inet 196.38.113.7 netmask 0x broadcast 196.38.113.7 inet 196.38.113.8 netmask 0x broadcast 196.38.113.8 inet 196.38.113.9 netmask 0x broadcast 196.38.113.9 inet 196.38.113.10 netmask 0x broadcast 196.38.113.10 inet 196.38.113.11 netmask 0x broadcast 196.38.113.11 inet 10.0.1.4 netmask 0xff00 broadcast 10.0.1.255 inet 10.0.1.5 netmask 0x broadcast 10.0.1.5 ether 08:00:08:00:08:00 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff00 Note how 196.38.113.2 (the machine's real address) has a netmask of 0xffe0, or 255.255.255.224, and the other addresses in this range (all of them aliases) have 0x, 255.255.255.255. Then look at 10.0.1.4, which is an alias too. It has a netmask of 0xff00, or 255.255.255.0. Now look at 10.0.1.5, an alias used for serving intranet web content to legacy machines. Again, a netmask of 0x. The reason for this is that 10.0.1.4, even though being an alias, is the first address the machine handles on that subnet. Just as 196.38.113.2 is the first address the machine has on the public subnet. Rule of thumb: First address on a subnet, alias or not, has the proper subnet netmask. Every other address on the subnet following that, has 0x, or 255.255.255.255. Will Thanks for clarifying this, Will. :) That was a very lucid and helpful explanation. - Mark To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Bizarre Networking Problem
I have a really weird networking issue on my firewall box. The machine in question has an ethernet facing a cisco facing the Internet and an ethernet facing the LAN plugged into a 3com 100Mbit switch. My LAN has all of the servers and most of the workstations sitting in the /24 that I've had for 10 years. Some of the newer workstations are now sitting on a /24 that I got from one of my providers when I filled up the old space. On xl0, the LAN ether, I simply added one of the new /24's to the interface with an ifconfig -alias and thought everything was good. And it was for users that only use the LAN for e-mail and www. But when I added some users that started messing around with 25MB pppts or 100MB .docs, the performance became pathetic, like in the single or low double digit kbps. The very same computer, can download a 100MB file from the 'net over a T1 faster than it can get a 50MB file off of my Samba based BSD file server. If I change the machines IP to one in the old /24 everything is fine again. Now it gets really weird. Today, one of my associates was investigating this problem and doing the experiments that document the above facts on two different machine. He called me and told me what he found. I logged into the firewall and started running tcpdump against the one address and also looking at the firewall logs to make sure I wasn't firewalling my own network. A few minutes later one of the users afflicted by this issue called to thank me for fixing the problem. I said eh? I haven't done anything other than look at the problem and I'm stumped. He says whatever, works great now! My associate confirmed this on another machine. Well, it is true, I *did* do something: I put xl0 into promiscuous mode. But why oh why is that fixing what should not even be a problem to begin with? Any klews cheerfully accepted (including hitting me with a clue-by-4 if I'm missing something obvious). -- Joseph F. Noonan Rigaku/MSC Inc. [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Bizarre Networking Problem
Joseph Noonan wrote: I have a really weird networking issue on my firewall box. The machine in question has an ethernet facing a cisco facing the Internet and an ethernet facing the LAN plugged into a 3com 100Mbit switch. My LAN has all of the servers and most of the workstations sitting in the /24 that I've had for 10 years. Some of the newer workstations are now sitting on a /24 that I got from one of my providers when I filled up the old space. On xl0, the LAN ether, I simply added one of the new /24's to the interface with an ifconfig -alias and thought everything was good. And it was for users that only use the LAN for e-mail and www. But when I added some users that started messing around with 25MB pppts or 100MB .docs, the performance became pathetic, like in the single or low double digit kbps. The very same computer, can download a 100MB file from the 'net over a T1 faster than it can get a 50MB file off of my Samba based BSD file server. If I change the machines IP to one in the old /24 everything is fine again. Now it gets really weird. Today, one of my associates was investigating this problem and doing the experiments that document the above facts on two different machine. He called me and told me what he found. I logged into the firewall and started running tcpdump against the one address and also looking at the firewall logs to make sure I wasn't firewalling my own network. A few minutes later one of the users afflicted by this issue called to thank me for fixing the problem. I said eh? I haven't done anything other than look at the problem and I'm stumped. He says whatever, works great now! My associate confirmed this on another machine. Well, it is true, I *did* do something: I put xl0 into promiscuous mode. But why oh why is that fixing what should not even be a problem to begin with? Any klews cheerfully accepted (including hitting me with a clue-by-4 if I'm missing something obvious). Somewhat of a shot in the dark, but ... Is the routing possibly messed up such that an attempt to connect to the aliased IP is being routed through the machine to the other IP on the same interface? I don't see why this would cause such terrible performance, but it's the best guess I have with the information you provide. Perhaps some output form 'netstat -rn' and 'ifconfig' might provoke some more useful answers. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
