Network bug in FreeBSD 4.4 STABLE

Network bug in FreeBSD 4.4 STABLE

Post by Pedro Paulo Oliveira » Sat, 10 Nov 2001 01:47:46



I'm using FreeBSD-4.4 STABLE as a transparent proxy.

I've noticed an easy to reproduce error

Install squid 2.4-STABLE2 as transparent proxy on 3128

My firewall rules are:
00049  1275  106743 allow tcp from 200.9.95.6 to any
00050     0       0 fwd 127.0.0.1,3128 tcp from any to any 80
60000 24151 4774860 allow ip from any to any
65535    32    4426 allow ip from any to any

My /etc/rc.conf are:

# This file now contains just the overrides from /etc/defaults/rc.conf
# please make all changes to this file.

# Enable network daemons for user convenience.
# -- sysinstall generated deltas -- #
hostname="filter.incor.usp.br"
sendmail_enable="YES"
defaultrouter="200.9.95.4"
sshd_enable="YES"
inetd_enable="YES"
gateway_enable="YES"
ifconfig_rl0="inet 200.9.95.6 netmask 255.255.255.0"
router_enable="NO"

The resolv.conf are right and the proxy works for some minutes and stops working.

Every tcp connection I try to establish returns: Can't assign requested address

For instance:
telnet localhost 21
Can't assign requested address

Squid also returns Can't assign requested address

Can anyone know a patch for this?

Pedro Paulo Jr

 
 
 

Network bug in FreeBSD 4.4 STABLE

Post by Daniel Rud » Sat, 10 Nov 2001 02:03:45



Quote:

> I'm using FreeBSD-4.4 STABLE as a transparent proxy.

> I've noticed an easy to reproduce error

> Install squid 2.4-STABLE2 as transparent proxy on 3128

> My firewall rules are:
> 00049  1275  106743 allow tcp from 200.9.95.6 to any
> 00050     0       0 fwd 127.0.0.1,3128 tcp from any to any 80
> 60000 24151 4774860 allow ip from any to any
> 65535    32    4426 allow ip from any to any

> My /etc/rc.conf are:

> # This file now contains just the overrides from /etc/defaults/rc.conf
> # please make all changes to this file.

> # Enable network daemons for user convenience.
> # -- sysinstall generated deltas -- #
> hostname="filter.incor.usp.br"
> sendmail_enable="YES"
> defaultrouter="200.9.95.4"
> sshd_enable="YES"
> inetd_enable="YES"
> gateway_enable="YES"
> ifconfig_rl0="inet 200.9.95.6 netmask 255.255.255.0"
> router_enable="NO"

> The resolv.conf are right and the proxy works for some minutes and stops working.

> Every tcp connection I try to establish returns: Can't assign requested address

> For instance:
> telnet localhost 21
> Can't assign requested address

> Squid also returns Can't assign requested address

> Can anyone know a patch for this?

> Pedro Paulo Jr

I have yet to find a clue as to why this happens.  I have been running
4.4-STABLE for awhile now myself and yesterday was the first day that I
noticed the problem.  I couldn't telnet into the box.  On the console
there is a list of messages that state inetd: telnet {Public IP Addr}
21: Can't assign requested address.  Anyone knows why this is
happening?  A reboot seems to have solved the problem.  BTW, which
network driver are you using?
--
Daniel Rudy
Reply to dcrudy at aol dot com.

*!*!* DO NOT HIT REPLY *!*!*
ALL EMAIL SENT TO REPLY ADDRESS WILL BE DELETED!

 
 
 

Network bug in FreeBSD 4.4 STABLE

Post by Daniel Rud » Sat, 10 Nov 2001 16:09:18




> > I'm using FreeBSD-4.4 STABLE as a transparent proxy.

> > I've noticed an easy to reproduce error

> > Install squid 2.4-STABLE2 as transparent proxy on 3128

> > My firewall rules are:
> > 00049  1275  106743 allow tcp from 200.9.95.6 to any
> > 00050     0       0 fwd 127.0.0.1,3128 tcp from any to any 80
> > 60000 24151 4774860 allow ip from any to any
> > 65535    32    4426 allow ip from any to any

> > My /etc/rc.conf are:

> > # This file now contains just the overrides from /etc/defaults/rc.conf
> > # please make all changes to this file.

> > # Enable network daemons for user convenience.
> > # -- sysinstall generated deltas -- #
> > hostname="filter.incor.usp.br"
> > sendmail_enable="YES"
> > defaultrouter="200.9.95.4"
> > sshd_enable="YES"
> > inetd_enable="YES"
> > gateway_enable="YES"
> > ifconfig_rl0="inet 200.9.95.6 netmask 255.255.255.0"
> > router_enable="NO"

> > The resolv.conf are right and the proxy works for some minutes and stops working.

> > Every tcp connection I try to establish returns: Can't assign requested address

> > For instance:
> > telnet localhost 21
> > Can't assign requested address

> > Squid also returns Can't assign requested address

> > Can anyone know a patch for this?

> > Pedro Paulo Jr

> I have yet to find a clue as to why this happens.  I have been running
> 4.4-STABLE for awhile now myself and yesterday was the first day that I
> noticed the problem.  I couldn't telnet into the box.  On the console
> there is a list of messages that state inetd: telnet {Public IP Addr}
> 21: Can't assign requested address.  Anyone knows why this is
> happening?  A reboot seems to have solved the problem.  BTW, which
> network driver are you using?
> --
> Daniel Rudy
> Reply to dcrudy at aol dot com.

> *!*!* DO NOT HIT REPLY *!*!*
> ALL EMAIL SENT TO REPLY ADDRESS WILL BE DELETED!

Here's an update.  I found this in my logs:

Nov  7 12:38:43 wildfire /kernel: Doing initial network setup:
Nov  7 12:38:43 wildfire /kernel: hostname
Nov  7 12:38:43 wildfire /kernel: .
Nov  7 12:38:43 wildfire /kernel: ad0: READ command timeout tag=0 serv=0
- resetting
Nov  7 12:38:43 wildfire /kernel: ata0: resetting devices .. done
Nov  7 12:38:43 wildfire /kernel: ad0: read interrupt arrived earlyad0:
read error detected (too) late
Nov  7 12:38:43 wildfire /kernel: Segmentation fault
Nov  7 12:38:43 wildfire /kernel: - core dumped
Nov  7 12:38:43 wildfire /kernel:
Nov  7 12:38:43 wildfire /kernel: Segmentation fault
Nov  7 12:38:43 wildfire /kernel: - core dumped
Nov  7 12:38:43 wildfire /kernel:
Nov  7 12:38:43 wildfire /kernel: Segmentation fault
Nov  7 12:38:43 wildfire /kernel: - core dumped
Nov  7 12:38:43 wildfire /kernel:
Nov  7 12:38:43 wildfire /kernel: Segmentation fault
Nov  7 12:38:43 wildfire /kernel: - core dumped
Nov  7 12:38:43 wildfire /kernel:
Nov  7 12:38:43 wildfire /kernel: Segmentation fault
Nov  7 12:38:43 wildfire /kernel: - core dumped
Nov  7 12:38:43 wildfire /kernel:
Nov  7 12:38:43 wildfire /kernel: Segmentation fault
Nov  7 12:38:43 wildfire /kernel: - core dumped
Nov  7 12:38:43 wildfire /kernel:
Nov  7 12:38:43 wildfire /kernel: Firewall rules loaded, starting divert
daemons:
Nov  7 12:38:43 wildfire /kernel: natd
Nov  7 12:38:43 wildfire /kernel: natd:
Nov  7 12:38:43 wildfire /kernel: Unable to bind divert socket.
Nov  7 12:38:43 wildfire /kernel: :
Nov  7 12:38:43 wildfire /kernel: Can't assign requested address
Nov  7 12:38:43 wildfire /kernel: .

I don't think that it is the harddisk.  Any ideas?

--
Daniel Rudy
Reply to dcrudy at aol dot com.

*!*!* DO NOT HIT REPLY *!*!*
ALL EMAIL SENT TO REPLY ADDRESS WILL BE DELETED!

 
 
 

Network bug in FreeBSD 4.4 STABLE

Post by Pedro Paulo Oliveira » Sat, 10 Nov 2001 22:19:52


I have already solved my problem.

One of the applications are allocating sockets without shutdown the socket.
But this bug didn't happened in previous FreeBSD STABLE Version.

Maybe something has changed and your problem can be appearing now.

Pedro Paulo




> > > I'm using FreeBSD-4.4 STABLE as a transparent proxy.

> > > I've noticed an easy to reproduce error

> > > Install squid 2.4-STABLE2 as transparent proxy on 3128

> > > My firewall rules are:
> > > 00049  1275  106743 allow tcp from 200.9.95.6 to any
> > > 00050     0       0 fwd 127.0.0.1,3128 tcp from any to any 80
> > > 60000 24151 4774860 allow ip from any to any
> > > 65535    32    4426 allow ip from any to any

> > > My /etc/rc.conf are:

> > > # This file now contains just the overrides from /etc/defaults/rc.conf
> > > # please make all changes to this file.

> > > # Enable network daemons for user convenience.
> > > # -- sysinstall generated deltas -- #
> > > hostname="filter.incor.usp.br"
> > > sendmail_enable="YES"
> > > defaultrouter="200.9.95.4"
> > > sshd_enable="YES"
> > > inetd_enable="YES"
> > > gateway_enable="YES"
> > > ifconfig_rl0="inet 200.9.95.6 netmask 255.255.255.0"
> > > router_enable="NO"

> > > The resolv.conf are right and the proxy works for some minutes and stops working.

> > > Every tcp connection I try to establish returns: Can't assign requested address

> > > For instance:
> > > telnet localhost 21
> > > Can't assign requested address

> > > Squid also returns Can't assign requested address

> > > Can anyone know a patch for this?

> > > Pedro Paulo Jr

> > I have yet to find a clue as to why this happens.  I have been running
> > 4.4-STABLE for awhile now myself and yesterday was the first day that I
> > noticed the problem.  I couldn't telnet into the box.  On the console
> > there is a list of messages that state inetd: telnet {Public IP Addr}
> > 21: Can't assign requested address.  Anyone knows why this is
> > happening?  A reboot seems to have solved the problem.  BTW, which
> > network driver are you using?
> > --
> > Daniel Rudy
> > Reply to dcrudy at aol dot com.

> > *!*!* DO NOT HIT REPLY *!*!*
> > ALL EMAIL SENT TO REPLY ADDRESS WILL BE DELETED!

> Here's an update.  I found this in my logs:

> Nov  7 12:38:43 wildfire /kernel: Doing initial network setup:
> Nov  7 12:38:43 wildfire /kernel: hostname
> Nov  7 12:38:43 wildfire /kernel: .
> Nov  7 12:38:43 wildfire /kernel: ad0: READ command timeout tag=0 serv=0
> - resetting
> Nov  7 12:38:43 wildfire /kernel: ata0: resetting devices .. done
> Nov  7 12:38:43 wildfire /kernel: ad0: read interrupt arrived earlyad0:
> read error detected (too) late
> Nov  7 12:38:43 wildfire /kernel: Segmentation fault
> Nov  7 12:38:43 wildfire /kernel: - core dumped
> Nov  7 12:38:43 wildfire /kernel:
> Nov  7 12:38:43 wildfire /kernel: Segmentation fault
> Nov  7 12:38:43 wildfire /kernel: - core dumped
> Nov  7 12:38:43 wildfire /kernel:
> Nov  7 12:38:43 wildfire /kernel: Segmentation fault
> Nov  7 12:38:43 wildfire /kernel: - core dumped
> Nov  7 12:38:43 wildfire /kernel:
> Nov  7 12:38:43 wildfire /kernel: Segmentation fault
> Nov  7 12:38:43 wildfire /kernel: - core dumped
> Nov  7 12:38:43 wildfire /kernel:
> Nov  7 12:38:43 wildfire /kernel: Segmentation fault
> Nov  7 12:38:43 wildfire /kernel: - core dumped
> Nov  7 12:38:43 wildfire /kernel:
> Nov  7 12:38:43 wildfire /kernel: Segmentation fault
> Nov  7 12:38:43 wildfire /kernel: - core dumped
> Nov  7 12:38:43 wildfire /kernel:
> Nov  7 12:38:43 wildfire /kernel: Firewall rules loaded, starting divert
> daemons:
> Nov  7 12:38:43 wildfire /kernel: natd
> Nov  7 12:38:43 wildfire /kernel: natd:
> Nov  7 12:38:43 wildfire /kernel: Unable to bind divert socket.
> Nov  7 12:38:43 wildfire /kernel: :
> Nov  7 12:38:43 wildfire /kernel: Can't assign requested address
> Nov  7 12:38:43 wildfire /kernel: .

> I don't think that it is the harddisk.  Any ideas?

 
 
 

1. Network bug - FreeBSD 4.4 STABLE

I'm using FreeBSD-4.4 STABLE as a transparent proxy.

I've noticed an easy to reproduce error

Install squid 2.4-STABLE2 as transparent proxy on 3128

My firewall rules are:
00049  1275  106743 allow tcp from 200.9.95.6 to any
00050     0       0 fwd 127.0.0.1,3128 tcp from any to any 80
60000 24151 4774860 allow ip from any to any
65535    32    4426 allow ip from any to any

My /etc/rc.conf are:

# This file now contains just the overrides from /etc/defaults/rc.conf
# please make all changes to this file.

# Enable network daemons for user convenience.
# -- sysinstall generated deltas -- #
hostname="filter.incor.usp.br"
sendmail_enable="YES"
defaultrouter="200.9.95.4"
sshd_enable="YES"
inetd_enable="YES"
gateway_enable="YES"
ifconfig_rl0="inet 200.9.95.6 netmask 255.255.255.0"
router_enable="NO"

The resolv.conf are right and the proxy works for some minutes and stops working.

Every tcp connection I try to establish returns: Can't assign requested address

For instance:
telnet localhost 21
Can't assign requested address

Squid also returns Can't assign requested address

Can anyone know a patch for this?

Pedro Paulo Jr

2. Mandrake 7.2 install problem

3. FreeBSD 4.4-20011111-STABLE bug?

4. Measuring data transfer over a NIC

5. Vmware2 and FreeBSD 4.4-STABLE network trouble

6. S3 Virge video driver

7. XFree86 4.1 Problem with FreeBSD 4.4-STABLE

8. Sending email with attachments via MIME

9. FreeBSD 4.4 - STABLE lockup

10. New FreeBSD-stable 4.4 release?

11. problems with FreeBSD 4.4-stable- HELP

12. Different keymap on FreeBSD 4.4 stable won't work