On Fri, February 10, 2006 20:10, Jon Simola wrote: > On 2/9/06, Per-Olov Sjöholm <[EMAIL PROTECTED]> wrote: > >> Look at the following output: >> [EMAIL PROTECTED]:~#ifconfig fxp0 inet alias 192.168.21.2 netmask >> 255.255.255.0 >> broadcast 192.168.21.255 up >> [EMAIL PROTECTED]:~#ifconfig fxp0 inet alias 192.168.22.2 netmask >> 255.255.255.0 >> broadcast 192.168.22.255 up >> [EMAIL PROTECTED]:~#ifconfig vlan0 inet 192.168.21.2 netmask 255.255.255.0 >> broadcast >> 192.168.21.255 vlan 21 vlandev fxp0 description "VLAN 21" >> [EMAIL PROTECTED]:~#ifconfig vlan1 inet 192.168.22.2 netmask 255.255.255.0 >> broadcast >> 192.168.22.255 vlan 22 vlandev fxp0 description "VLAN 22" > > Something is wrong here, you're assigning the same IP to both the vlan > and fxp interfaces. >
I must have been sleeping here. After reading your post I did *exactly* the same thing but didn't create an IP alias on fxp0 first. Then it worked. Don't understand why I first did that. Maybe I was reading the man pages without using my brain... THANKS!! >> [EMAIL PROTECTED]:~#ifconfig carp0 inet 192.168.21.1 netmask 255.255.255.0 >> broadcast >> 192.168.21.255 vhid 21 carpdev vlan0 description "GW 21" >> ifconfig: SIOCAIFADDR: Can't assign requested address >> [EMAIL PROTECTED]:~#ifconfig carp1 inet 192.168.22.1 netmask 255.255.255.0 >> broadcast >> 192.168.22.255 vhid 22 carpdev vlan1 description "GW 22" >> ifconfig: SIOCAIFADDR: Can't assign requested address >> >> Why can't it assign the "carpdev vlan0" and "carpdev vlan1" ? > > Which part of "SIOCAIFADDR: Can't assign requested address" suggests > that the carpdev is the failing part? The above looks like you're > pasting 6 lines into a shell prompt and the errors are out of order. Yes, I was pasting 6 shell command in order. And the messages are in order as well. Which means the error output i related to the command just before the error output. The problem was *only* the one mentioned above with the ip alias on fxp0... > >> fxp0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu >> 1500 >> lladdr 00:d0:b7:c8:cb:eb >> groups: egress >> media: Ethernet autoselect (100baseTX full-duplex) >> status: active >> inet 192.168.11.20 netmask 0xfffffc00 broadcast 192.168.11.255 >> inet6 fe80::2d0:b7ff:fec8:cbeb%fxp0 prefixlen 64 scopeid 0x1 > > This doesn't match the ifconfig alias commands above for fxp0. No. And there is no problem do assign other networks to the same nic... I Did my tests on a desktop OBSD 3.8 with one nic and decided to add some more alias networks to the fxp0 for this laboration. But this was as said not the problem... > >> vlan0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu >> 1500 >> lladdr 00:d0:b7:c8:cb:eb >> description: VLAN 21 >> vlan: 21 parent interface: fxp0 >> groups: vlan >> inet6 fe80::2d0:b7ff:fec8:cbeb%vlan0 prefixlen 64 scopeid 0x12 >> inet 192.168.21.2 netmask 0xffffff00 broadcast 192.168.21.255 > > Do you need IP addresses on your vlan devices? carp will bind fine to > any interface with the carpdev parameter. Hmmm. If it's possible I can maybe live without IP:s on some VLAN devices. Good info. > >> carp0: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500 >> description: GW 21 >> carp: INIT carpdev vlan0 vhid 21 advbase 1 advskew 0 >> groups: carp >> carp1: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500 >> description: GW 22 >> carp: INIT carpdev vlan1 vhid 22 advbase 1 advskew 0 >> groups: carp > > That looks normal for a carp device without an IP bound to it yet. > >> [EMAIL PROTECTED]:~#netstat -rn >> Routing tables >> >> Internet: >> Destination Gateway Flags Refs Use Mtu >> Interface >> default 192.168.8.1 UGS 6 1401 - >> fxp0 >> 127/8 127.0.0.1 UGRS 0 0 33224 >> lo0 >> 127.0.0.1 127.0.0.1 UH 1 0 33224 >> lo0 >> 192.168.8/22 link#1 UC 2 0 - >> fxp0 >> 192.168.8.1 0:0:5e:0:1:2 UHLc 1 0 - >> fxp0 >> 192.168.8.2 0:e:c:a9:a8:8 UHLc 0 5 - >> fxp0 >> 192.168.21/24 link#1 UC 0 0 - >> fxp0 >> 192.168.22/24 link#1 UC 0 0 - >> fxp0 >> 224/4 127.0.0.1 URS 0 0 33224 >> lo0 > > Has this been snipped? On my boxes local addresses and aliases show up > in netstat output. Yes > > -- > Jon Simola > Systems Administrator > ABC Communications >
