freebsd-net@freebsd.org
Hello, I was adding a static route and "accidentally" put an extra number 1 after the command, like this: route add -net 192.168.0.100 192.168.0.200 255.255.255.255 1 netstat -rn prints: Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire 0.0.0.0&0x1192.168.0.200 UGS 00 bge0 I tried to remove this route without success, either with: route delete -net 192.168.0.100 192.168.0.200 255.255.255.255 1 or route delete -net 192.168.0.100 192.168.0.200 255.255.255.255 I had to run route flush to get rid of it. Anyone has any clues? And also, how come a route like this being interpreted as the default route? This happened on a 7.3-RELEASE and I also tested on an old 6.2-RELEASE without being able to remove the route. The only difference is that it shows as 0.0.0.0&0x1 on 7.3 and as 0&0x1 on 6.2. Thank you in advance, Tobias. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
freebsd-net@freebsd.org
[...] route add -net 192.168.0.100 192.168.0.200 255.255.255.255 1 Destination Gateway Flags Refs Use Netif Expire 0.0.0.0&0x1 192.168.0.200 UGS 0 0 bge Try: route delete 0.0.0.0 -netmask 0.0.0.1 It worked! [...] A 0.0.0.0/0.0.0.1 route matches every IP with bit 0 clear and is half the size of a 0.0.0.0/0.0.0.0 route - which is pretty big. Something like: 0.0.0.0 0.0.0.2 0.0.0.4 ... 255.255.255.252 255.255.255.254 HTH, Nikos I agree. What I don't understand is how the command I typed could become 0.0.0.0/0.0.0.1 in the routing table. Thank you, Tobias. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ipfw can't be disabled for IPv56
Kevin Oberman wrote:
Running 7-STABLE of April 10, if I disable the firewall ('sysctl
net.inet.ip.fw.enable=0'), IPv4 traffic passes, but IPv6 will not. I had
to add a "allow ip from any to any" rule to get IPv6 to work pass
traffic. (Since I was accessing the system in question via IPv6, this
was a bit annoying!)
Am I missing anything? The rc.subr script for ipfw just sets the sysctl I
did when it stops the firewall.
# sysctl -a | grep fw
net.inet.ip.fw.dyn_keepalive: 1
net.inet.ip.fw.dyn_short_lifetime: 5
net.inet.ip.fw.dyn_udp_lifetime: 10
net.inet.ip.fw.dyn_rst_lifetime: 1
net.inet.ip.fw.dyn_fin_lifetime: 1
net.inet.ip.fw.dyn_syn_lifetime: 20
net.inet.ip.fw.dyn_ack_lifetime: 300
net.inet.ip.fw.static_count: 8
net.inet.ip.fw.dyn_max: 4096
net.inet.ip.fw.dyn_count: 0
net.inet.ip.fw.curr_dyn_buckets: 256
net.inet.ip.fw.dyn_buckets: 256
net.inet.ip.fw.verbose_limit: 0
net.inet.ip.fw.verbose: 1
net.inet.ip.fw.debug: 1
net.inet.ip.fw.one_pass: 1
net.inet.ip.fw.autoinc_step: 100
net.inet.ip.fw.enable: 1
net.link.ether.ipfw: 0
net.inet6.ip6.fw.enable: 1 < voila!!!
net.inet6.ip6.fw.debug: 1
net.inet6.ip6.fw.verbose: 1
net.inet6.ip6.fw.verbose_limit: 0
net.inet6.ip6.fw.deny_unknown_exthdrs: 1
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
rl driver and 4GB RAM
Hello! We recently bought a Dell Server with 4GB RAM. Then, we installed FreeBSD 6.1/i386 but it only detects 3.5GB of RAM. So we recompiled the kernel with PAE option and now we have 4GB available. Onboard NIC (em0) works fine both with GENERIC and PAE kernel, but as we need a second 100 Mbit NIC, we plugged a Realtek 8139D board, but it doesn't work with PAE kernel (GENERIC is fine). If you do a tcpdump, you can see packets and arp requests on the network, but we can't ping anything. It seems that we can only "listen" on rl0 but not "speak". Once we reboot the server with GENERIC kernel, the NIC works fine. We also tried 5.4/amd64, but the behaviour is the same as we have with PAE. Any suggestions? Could it be a driver related problem, so if we change to another NIC it may work? Thank you in advance, Tobias. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pipe dropping lots of packets
Hello! Alex Povolotsky wrote: Hello! I'm trying to set up FreeBSD-based router, and got troubles with bandwidth limiting. My queues drops lots of packets. [23:38] gw:~ # ipfw pipe 200 config bw 30mbit/s queue 100 You should use 30Mbit/s (with capital M). [23:42] gw:~ # ipfw add 600 pipe 200 ip from any to any out via vlan333 00600 pipe 200 ip from any to any out via vlan333 seems to be easy. now [23:43] gw:~ # ipfw zero Accounting cleared. make sure we'll catch packets out of pipe [23:43] gw:~ # sysctl net.inet.ip.fw.one_pass net.inet.ip.fw.one_pass: 0 and, waiting a bit [23:43] gw:~ # ipfw show | grep vlan333 00600 2010140730 pipe 200 ip from any to any out via vlan333 00700 0 0 allow ip from any to table(1) via vlan333 00710840142335 allow ip from table(1) to any via vlan333 whoops! No packets left pipe part of ipfw pipe list 00200: 30.000 bit/s 0 ms 100 sl. 1 queues (1 buckets) droptail See, 30 bit/s will drop a lot of packets! ;) Regards, Tobias. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Remote Boot
Hello, I am trying to boot a FreeBSD diskless client with no success. Actually, I can boot the client, the kernel is downloaded and begins to boot. Then it tries to reach the DHCP/BOOT server, but this never occurs and the machine repeats the following messages forever: bootpc_call: sosend: 13 state DHCP/BOOTP timeout for server 255.255.255.255 I connected both machines (server and client) with a crossover cable and ran tcpdump on server. Once the kernel is downloaded, there isn't any more talking on the network so the client is not asking for a DHCP/BOOTP server as it should be, or as it says to be. I made these tests with FreeBSD 4.8 and then switched back to 4.4 but got the same behaviour with both versions. With version 5.0, the kernel was downloaded but it didn't boot, so I gave up 5.x. The NIC's are Realtek 8139 detected as rl0 on client and also on server. BTW, I also tried an ed0 interface but it didn't change anything. Anyone could give a hand here? The only thing I can imagine is something wrong with diskless kernel, but I've compiled with the handbook instructions: options BOOTP # Use BOOTP to obtain IP address/hostname options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info options BOOTP_COMPAT # Workaround for broken bootp daemons. Any clues? Thank you in advance! Best regards, -- Tobias. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Remote Boot
Hi Atanu, you're right. I've recompiled the diskless kernel and now it's working fine. I also would like to thank everybody who took time to help me with this issue. Thank you all! Best regards, Tobias. Atanu Ghosh wrote: > > >From my notes when trying to get diskless booting working: > > We usually have the firewall and dummynet enabled in our configs. The > default is therefore not to allow any packets in or out. This stops > the DHCP packets leaving a diskless kernel. Override this default. > > options IPFIREWALL_DEFAULT_TO_ACCEPT > > Atanu. > > >>>>> "Tobias" == Tobias P Santos <[EMAIL PROTECTED]> writes: > > Tobias> Hello, I am trying to boot a FreeBSD diskless client with > Tobias> no success. Actually, I can boot the client, the kernel > Tobias> is downloaded and begins to boot. Then it tries to reach > Tobias> the DHCP/BOOT server, but this never occurs and the > Tobias> machine repeats the following messages forever: > > Tobias> bootpc_call: sosend: 13 state DHCP/BOOTP timeout > Tobias> for server 255.255.255.255 > > Tobias> I connected both machines (server and client) with a > Tobias> crossover cable and ran tcpdump on server. Once the kernel > Tobias> is downloaded, there isn't any more talking on the network > Tobias> so the client is not asking for a DHCP/BOOTP server as it > Tobias> should be, or as it says to be. > > Tobias> I made these tests with FreeBSD 4.8 and then switched back > Tobias> to 4.4 but got the same behaviour with both versions. > > Tobias> With version 5.0, the kernel was downloaded but it didn't > Tobias> boot, so I gave up 5.x. > > Tobias> The NIC's are Realtek 8139 detected as rl0 on client and > Tobias> also on server. BTW, I also tried an ed0 interface but it > Tobias> didn't change anything. > > Tobias> Anyone could give a hand here? The only thing I can > Tobias> imagine is something wrong with diskless kernel, but I've > Tobias> compiled with the handbook instructions: > > Tobias> options BOOTP # Use BOOTP to obtain IP address/hostname > Tobias> options BOOTP_NFSROOT # NFS mount root filesystem using > Tobias> BOOTP info options BOOTP_COMPAT # Workaround for broken > Tobias> bootp daemons. > > Tobias> Any clues? > > Tobias> Thank you in advance! Best regards, -- Tobias. > Tobias> ___ > Tobias> [EMAIL PROTECTED] mailing list > Tobias> http://lists.freebsd.org/mailman/listinfo/freebsd-net To > Tobias> unsubscribe, send any mail to > Tobias> "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
IPFW issue: skip past end of rules
Hello, I have a gateway limiting the bandwidth of my customers. Everything is working fine, but I got some messages in the log file, see: [...] Dec 1 15:04:55 proxy /kernel: +++ ipfw: ouch!, skip past end of rules, denying packet Dec 1 15:06:17 proxy last message repeated 90 times Dec 1 15:19:24 proxy last message repeated 41 times Dec 1 15:33:58 proxy last message repeated 142 times Dec 1 15:38:57 proxy last message repeated 121 times [...] Here are my rules: 00100344 101154 allow ip from any to any via lo0 00200 0 0 deny ip from any to 127.0.0.0/8 00300450 18000 deny ip from 127.0.0.0/8 to any 00400 99711390018 pipe 1 ip from any to any MAC any 00:00:00:00:00:00 in 00500 12282 11562920 pipe 2 ip from any to any MAC 00:00:00:00:00:00 any out 00600 0 0 pipe 3 ip from any to any MAC any 11:11:11:11:11:11 in 00700 0 0 pipe 4 ip from any to any MAC 11:11:11:11:11:11 any out 00800 0 0 pipe 5 ip from any to any MAC any 22:22:22:22:22:22 in 00900 0 0 pipe 6 ip from any to any MAC 22:22:22:22:22:22 any out 01000 0 0 pipe 7 ip from any to any MAC any 33:33:33:33:33:33 in 01100 0 0 pipe 8 ip from any to any MAC 33:33:33:33:33:33 any out 012002336717 1482414132 divert 8668 ip from any to any via vr0 650009272277 5914106630 allow ip from any to any 65535318 177373 deny ip from any to any Am I missing something? I can't find information about this issue anywhere. Thank you in advance! Best regards, Tobias. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
