Re: why wont my vlan interface accept this /28 ?

2009-02-06 Thread Simen Stavdal 
Hello,

I've had a similar issue before, and cannot quite remember in detail, but
it was something like this ;

Check that you have a /etc/hostname.vlan203 config file, and modify the
netmask here.
Do you have any carp interfaces layered over vlan203 that may be
conflicting with the netmask?
If you do, correct this, and then issue a destroy on the carp interface
(if any), than the vlan interface, followed by sh /etc/netstart vlan203 ;
sh /etc/netstart carp203 (or other carp name if any).

So, summarised :
ifconfig | grep carp | grep vlan # Will tell you if you have vlandev 203
in use by any carp interfaces.
if you do, note the carp interface name (let's call it carp203).
Then, correct your /etc/hostname.vlan203 and /etc/hostname.carp203 files
with the correct netmask.
Then, issue a :
ifconfig carp203 destroy ; ifconfig vlan203 destroy ; sh /etc/netstart
vlan203 ; sh /etc/netstart carp203

This worked for me at least...

Cheers,
Simon

On Fri Feb 6 14:32 , Charlie Allom sent:

  Hi!

  There is some subtelty here which I cannot distinguish.. There is
  another host on the same segment with 94.228.79.226/0xfff0 if
  that
  helps? I will put a carpN on 94.228.79.225/28.

  anyway the problem is this: I can't seem to assign the /28 to this
  new
  vlan interface:

  13:16 trajan:~# ifconfig vlan203 inet 94.228.79.227
  13:16 trajan:~# ifconfig vlan203 inet 94.228.79.227 netmask
  0xfff8
  13:17 trajan:~# ifconfig vlan203 inet 94.228.79.227 netmask
  0xfff0
  ifconfig: SIOCAIFADDR: File exists

  whhaatt? others work?

  13:19 trajan:~# uname -a
  OpenBSD trajan.playlouder.com 4.3 GENERIC.MP+RAIDFRAME#2 i386

  13:24 trajan:~# ifconfig
  lo0: flags=8049 mtu 33208
  groups: lo
  inet 127.0.0.1 netmask 0xff00
  inet6 ::1 prefixlen 128
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
  em0: flags=8843 mtu 1500
  lladdr 00:30:48:33:52:fa
  description: mgmt
  media: Ethernet autoselect (1000baseT full-duplex,master)
  status: active
  inet 10.0.1.28 netmask 0xff00 broadcast 10.0.1.255
  inet6 fe80::230:48ff:fe33:52fa%em0 prefixlen 64 scopeid 0x1
  em1: flags=8843 mtu 1500
  lladdr 00:30:48:33:52:fb
  description: pfsync
  media: Ethernet autoselect (1000baseT
  full-duplex,master,rxpause,txpause)
  status: active
  inet 10.0.0.3 netmask 0xff00 broadcast 10.0.0.255
  inet6 fe80::230:48ff:fe33:52fb%em1 prefixlen 64 scopeid 0x2
  em2: flags=8943 mtu 1500
  lladdr 00:15:17:14:ec:9c
  description: trajan
  media: Ethernet autoselect (1000baseT full-duplex)
  status: active
  inet 193.34.28.3 netmask 0xfe00 broadcast 193.34.29.255
  inet6 fe80::215:17ff:fe14:ec9c%em2 prefixlen 64 scopeid 0x3
  inet6 2a01:450:1000:57ab::3 prefixlen 64
  em3: flags=8943 mtu 1500
  lladdr 00:15:17:14:ec:9d
  description: transit
  groups: egress
  media: Ethernet autoselect (1000baseT full-duplex)
  status: active
  inet 89.200.217.3 netmask 0xffe0 broadcast 89.200.217.31
  inet6 fe80::215:17ff:fe14:ec9d%em3 prefixlen 64 scopeid 0x4
  inet6 2a01:450:1000:10c8::3 prefixlen 64
  em4: flags=8943 mtu 1500
  lladdr 00:15:17:14:ec:9e
  media: Ethernet autoselect (1000baseT full-duplex)
  status: active
  inet6 fe80::215:17ff:fe14:ec9e%em4 prefixlen 64 scopeid 0x5
  em5: flags=8943 mtu 1500
  lladdr 00:15:17:14:ec:9f
  media: Ethernet autoselect (1000baseT full-duplex)
  status: active
  inet6 fe80::215:17ff:fe14:ec9f%em5 prefixlen 64 scopeid 0x6
  enc0: flags=0 mtu 1536
  pfsync0: flags=41 mtu 1460
  pfsync: syncdev: em1 syncpeer: 224.0.0.240 maxupd: 128
  groups: carp pfsync
  pflog0: flags=141 mtu 33208
  groups: pflog
  vlan203: flags=8843 mtu 1500
  lladdr 00:15:17:14:ec:9c
  vlan: 203 priority: 0 parent interface: em2
  groups: vlan
  inet6 fe80::215:17ff:fe14:ec9c%vlan203 prefixlen 64 scopeid 0xe
  carp0: flags=8843 mtu 1500
  lladdr 00:00:5e:00:01:15
  description: gateway
  carp: BACKUP carpdev em2 vhid 21 advbase 1 advskew 100
  groups: carp
  inet6 fe80::200:5eff:fe00:115%carp0 prefixlen 64 scopeid 0x9
  inet 193.34.28.1 netmask 0xfe00 broadcast 193.34.29.255
  carp1: flags=8843 mtu 1500
  lladdr 00:00:5e:00:01:16
  description: incoming gateway
  carp: BACKUP carpdev em3 vhid 22 advbase 1 advskew 100
  groups: carp
  inet6 fe80::200:5eff:fe00:116%carp1 prefixlen 64 scopeid 0xa
  inet 89.200.217.1 netmask 0xffe0 broadcast 89.200.217.31
  carp2: flags=8843 mtu 1500
  lladdr 00:00:5e:00:01:17
  description: ci-gateway
  carp: BACKUP carpdev em2 vhid 23 advbase 1 advskew 100
  groups: carp
  inet6 fe80::200:5eff:fe00:117%carp2 prefixlen 64 scopeid 0xb
  inet 193.34.29.1 netmask 0xff00 broadcast 193.34.29.255

  --
  020 7729 4797
  http://blog.playlouder.com/

-
FC% din egen, gratis e-postadresse pC% Start.no

Re: why wont my vlan interface accept this /28 ?

2009-02-06 Thread Charlie Allom 
On Fri, Feb 06, 2009 at 04:16:57PM +0100, Simen Stavdal wrote:
 Hello,
 
 I've had a similar issue before, and cannot quite remember in detail, but it
 was something like this ;

thanks Simon for that - it's similar but not the same issue. uux
[hmnbx4r...@gatekeeper.wzrd.com] on #openbsd sorted me out.

14:00 uux yeled: I think it is on 4.3.  routing table snafu.

You can't create an interface (on a vlan?) if the network is already in
your route table. I am sharing my routes on both firewalls with OSPF so
this is where the issue arises.

uux came up with the idea of installing the vlan interface on boot time
(ie rebooting the box) and getting around this problem.

Does anyone know if this has been fixed?

Regards,
  C.
-- 
 020 7729 4797
 http://blog.playlouder.com/