Forum - Connectivity across 2 interfaces :: SixXS - IPv6 Deployment & Tunnel Broker

Connectivity across 2 interfaces

Shadow Hawkins on Saturday, 06 February 2010 14:05:12

Hi! I enjoy SixXS ipv6 connectivity, but lately my topology has changed, such that one part of the network is ethernet, and the other is wifi. I thought that I would only have to change radvd.conf, but I have no connectivity from the wifi part to the wired. My laptop on the wifi get's an address and can ping6 the router, but pinging from the router to the laptop fails. Need less to say, connection between wired and wireless is non-existant. All help and comment is appreciated! Best regards, Sune Mlgaard

Connectivity across 2 interfaces

Shadow Hawkins on Tuesday, 09 February 2010 23:12:39

Is your router also your wireless access point, or is that a separate unit? In most home and small business I've seen, there is a "wireless router" that bridges the wired and wireless networks (one physical subnet). If you have a router that is separate from your wireless access point, does the access point describe itself as a router, and access point or a wireless bridge? Basically we need to figure out if you have one physical subnet or two. In most cases it's one, and no changes to radvd.conf should be necessary. If your wireless network is not bridged to the wired subnet, then you'll need another device to provide RA's on the wireless subnet. You say you can ping from the laptop to the router, but not the other way around. That sounds more like a firewall issue, but perhaps I misunderstood what you said.

Connectivity across 2 interfaces

Shadow Hawkins on Wednesday, 10 February 2010 10:55:39

Thank you for answering! The router is a Linux box, which acts as both regular and wireless router. I have assigned ipv6 addresses to both the wired and the wireless cards, however when I try to ping the laptop, it pings from the wired card, and can't get anywhere. Pinging from the laptop, though, gets through to the tunnel endpoint fine... Hope that helps?

Connectivity across 2 interfaces

Shadow Hawkins on Wednesday, 10 February 2010 14:52:41

Okay, in that case you have two options: 1 - Bridge the wired and wireless interfaces on the linux router. This would behave like the storebought home routers where the wired and wireless networks share the same prefix, but may be more complex in setup. 2 - Ensure that radvd is advertising on both interfaces, and each interface must have a different prefix. For example if your wireless interface prefix is 2001:db8::/64, then perhaps the wired interface prefix could be assigned 2001:db8:1::/64 . Ensure the address assigned to each interface is within the prefix radvd is advertising on that interface. This is simpler in setup in this case although perhaps more complex conceptually. I vote option 2 for ease in setup.

Connectivity across 2 interfaces

Shadow Hawkins on Wednesday, 10 February 2010 15:05:34

For example if your wireless interface prefix is 2001:db8::/64, then perhaps the wired interface prefix could be assigned 2001:db8:1::/64

Oops, let me correct that. I gave a prefix out of a different /48 which won't work. if your wireless interface prefix is 2001:db8::/64, then perhaps the wired interface prefix could be assigned 2001:db8:0:1::/64 . (If your subnet is 2001:db8::/48 , then any prefix must start with 2001:db8:0: .)

Connectivity across 2 interfaces

Shadow Hawkins on Monday, 15 February 2010 08:23:38

Still doesn't quite seem to work :-( Do I need to set any routes? And which address should I assign to the cards? My subnet prefix is 2001:16d8:ee1e::/48, and I have tried setting the wireless card to 2001:16d8:ee1e:0:1::1/64 with the prefix in radvd.conf as 200116d8:ee1e:0:1::/64, but the laptop still gets assigned a 2001:16d8:ee1e:0:22... address. Is this expected? Shouldn't it get a 2001:16d8:ee1e:0:1:... address instead? Sorry for my confusion, but thank you still, Sune

Connectivity across 2 interfaces

Jeroen Massar SixXS Staff

on Wednesday, 17 March 2010 11:01:52

2001:16d8:ee1e:0:1::1/64 == 2001:16d8:ee1e:0::/64 Count the number of parts, 2001:16d8 == 32 bits, ee1e:0 = another 32bits, thus together 2001:16d8:ee1e:0::/64 Your first /64 is: 2001:16d8:ee1e:0::/64 (or 2001:16d8:ee1e::/64) Your second 2001:16d8:ee1e:1::/64 Third etc: 2001:16d8:ee1e:2::/64 2001:16d8:ee1e:3::/64 2001:16d8:ee1e:4::/64 2001:16d8:ee1e:5::/64 ... 2001:16d8:ee1e:ffff::/64 65k of them...

Connectivity across 2 interfaces

Shadow Hawkins on Sunday, 21 March 2010 17:34:46

That did it - thank you so much :-D

Connectivity across 2 interfaces

Shadow Hawkins on Sunday, 21 March 2010 17:52:58

Bummer - I spoke too soon :-( laptop and server can ping6 each other, as can desktop and server, but pings between laptop and desktop get dropped :-( Could I have missed any route declarations on the server or something? Best regards and thanks, Sune

Connectivity across 2 interfaces

Jeroen Massar SixXS Staff

on Sunday, 21 March 2010 18:03:14

Show the routes of the hosts involved and maybe we can help debugging them ;)

Connectivity across 2 interfaces

Shadow Hawkins on Monday, 29 March 2010 00:52:25

Well, after reboots, things now work as they should, so I must have mucked something up while playing around :-$ Thank you for all you help! :-)

Connectivity across 2 interfaces

Shadow Hawkins on Wednesday, 17 March 2010 00:22:52

Sorry for bumping, but does anyone have an idea?

Please note Posting is only allowed when you are logged in.