Em 18-04-2014 15:04, Lubo Diakov escreveu: > Routing tables > > Internet: > Destination Gateway Flags Refs Use Mtu Prio Iface > default 188.126.4.1 UGS 1 7188 - 8 rl1 > 127/8 127.0.0.1 UGRS 0 0 33192 8 lo0 > 127.0.0.1 127.0.0.1 UH 1 0 33192 4 lo0 > 188.126.4/24 link#3 UC 2 0 - 4 rl1 > 188.126.4.1 00:30:48:b8:c5:83 UHLc 1 72 - 4 rl1 > 188.126.4.24 4c:00:10:3c:23:5c UHLc 0 6 - 4 lo0 > 192.168.6/24 link#1 UC 3 0 - 4 rl0 > 192.168.6.6 00:40:f4:44:07:56 UHLc 0 6 - 4 lo0 > 192.168.6.8 00:80:ad:00:7c:ca UHLc 1 44 - 4 rl0 > 192.168.6.9 00:80:ad:00:7c:ca UHLc 0 70 - 4 rl0 > 224/4 127.0.0.1 URS 0 0 33192 8 lo0 > > Internet6: > Destination Gateway > Flags Refs Use Mtu Prio Iface > ::/104 ::1 UGRS > 0 0 - 8 lo0 > ::/96 ::1 UGRS > 0 0 - 8 lo0 > ::1 ::1 UH > 14 0 33192 4 lo0 > ::127.0.0.0/104 ::1 UGRS > 0 0 - 8 lo0 > ::224.0.0.0/100 ::1 UGRS > 0 0 - 8 lo0 > ::255.0.0.0/104 ::1 UGRS > 0 0 - 8 lo0 > ::ffff:0.0.0.0/96 ::1 UGRS > 0 0 - 8 lo0 > 2002::/24 ::1 UGRS > 0 0 - 8 lo0 > 2002:7f00::/24 ::1 UGRS > 0 0 - 8 lo0 > 2002:e000::/20 ::1 UGRS > 0 0 - 8 lo0 > 2002:ff00::/24 ::1 UGRS > 0 0 - 8 lo0 > fe80::/10 ::1 UGRS > 0 0 - 8 lo0 > fe80::%rl0/64 link#1 UC > 0 0 - 4 rl0 > fe80::240:f4ff:fe44:756%rl0 00:40:f4:44:07:56 HL > 0 0 - 4 lo0 > fe80::%rl1/64 link#3 UC > 0 0 - 4 rl1 > fe80::4e00:10ff:fe3c:235c%rl1 4c:00:10:3c:23:5c HL > 0 0 - 4 lo0 > fe80::%lo0/64 fe80::1%lo0 U > 0 0 - 4 lo0 > fe80::1%lo0 link#5 UHL > 0 0 - 4 lo0 > fec0::/10 ::1 UGRS > 0 0 - 8 lo0 > ff01::/16 ::1 UGRS > 0 0 - 8 lo0 > ff01::%rl0/32 link#1 UC > 0 0 - 4 rl0 > ff01::%rl1/32 link#3 UC > 0 0 - 4 rl1 > ff01::%lo0/32 fe80::1%lo0 UC > 0 0 - 4 lo0 > ff02::/16 ::1 UGRS > 0 0 - 8 lo0 > ff02::%rl0/32 link#1 UC > 0 0 - 4 rl0 > ff02::%rl1/32 link#3 UC > 0 0 - 4 rl1 > ff02::%lo0/32 fe80::1%lo0 UC > 0 0 - 4 lo0 > > Is /etc/mygate the correct way to route on a system with two or more > NICs (IP addresses) or is it better to put route add commands in each > hostname file for the appropriate NIC? (i.e route traffic for the > internet via rl1, and traffic for 192.168.whatever via rl0) > > Something else I had not noticed before, the ISP has BGPd running > accrding to nmap under Ubuntu, which it occurred to me might explain a > lot of this, though again, it isn't logical why it works on Ubuntu but > not OpenBSD, but if I need for example a BGP client installed and > configured that might sort it out. No such client or server installed > under Ubuntu though, so that seems unlikely. > We still need dmesg, ifconfig and such. But I can tell you right know that I had the same issue some years ago. A linux worked while an OpenBSD didn't. Turned out, the ISP modem had it's own configuration wrong, where it should be a /29 it was a /30 if I'm not mistaken. On linux it worked because their networking stack is lazy. On OpenBSD it didn't, because if the netmask isn't right it will simply refuse to work. Specially when dealing with non RFC 1918 addresses. Your address are all valid internet ip addresses right? So take a look at your isp modem/router/whatever configuration. Specifically, check what your contract with them specify and what is actually configured.
Cheers, -- Giancarlo Razzolini GPG: 4096R/77B981BC
