Hi,
Thanks for the help. I haven't had the time to test this until now but
as one can expect, when you know how to use it, it works without much
struggle.
I still have some problem with my ral0 gets 'device timeout' after
reboot. Only way to remedy this (that I know of) is to bring ral0 down
On 2006/11/09 10:40, Reyk Floeter wrote:
> in this example, the you're clients lladdr will be removed from the
> cache after 10 seconds and can be re-learned on another interface.
a little different to standard switches then. if I trunk ath0+em0 with
the AP plugged into a switch and then plug em0
hi,
On Thu, Nov 09, 2006 at 01:44:26AM +0100, Markus Bergkvist wrote:
> First, I thought it was because fxp0 and ral0 on the host was on
> different sub-nets but now they are both on 192.168.0/24 and so is trunk0.
> So i added a bridge
> # ifconfig bridge0 create
> # brconfig bridge0 add fxp0 add
Reyk Floeter wrote:
> On Wed, Nov 08, 2006 at 01:01:39AM +0100, Markus Bergkvist wrote:
>
> don't do dhclient ral0, do a dhclient trunk0 after setting up trunk.
>
> # ifconfig fxp0 up
> # ifconfig ral0 nwid himmet_wlan up
> # ifconfig trunk0 trunkproto failover trunkport fxp0 trunkport ral0 up
>
> 192.168.0/24 link#1 UC 00 - fxp0
oh, you probably haven't deleted the IP address from fxp0 there.
(you also sometimes need to 'route change default X.X.X.X' when the
interface moves).
> Ok, some progress now. Doing what you suggested and rebooting and f
Short description of what actions I did on client that maps to entries
in attached file tcp_dump_host:
00:33:38, ifconfig ral0 up
00:33:41, dhclient ral0
00:37:09, ifconfig trunk0 trunkproto failover trunkport fxp0 trunkport ral0
subsequent ping to 192.168.0.1 gave the same error as described in
Simon Westphahl wrote:
Your interfaces need to be marked up and completely unconfigured.
In your case:
#cat /etc/hostname.fxp0
up
#cat /etc/hostname.ral0
up
#cat /etc/hostname.trunk0
inet 192.168.0.35 255.255.255.0 NONE trunkproto failover trunkport fxp0
trunkport ral0
Ok, some progress now
Markus Bergkvist wrote:
This is the post-trunk ifconfig:
...
fxp0: flags=8943 mtu 1500
lladdr 00:02:a5:b8:71:b5
trunk: trunkdev trunk0
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet6 fe80::202:a5ff:feb8:71b5%fxp0 prefixlen 64 scopeid
On Tue, Nov 07, 2006 at 11:50:16PM +0100, Markus Bergkvist wrote:
> Reyk Floeter wrote:
> >the trunk will use the mac address of it's primary trunkport, which is
> >fxp0 in your case. as soon as you add ral0 to the trunk it will also
> >use the trunk mac address (00:02:a5:b8:71:b5 from fxp0) for et
Stuart Henderson wrote:
> kill the old routing table entries (or reboot).
>
>
Ok, did a
# route flush
but that did not help. Not sure how to interpret the output from the
utililty but it seems to be ok, or?
The output is attached, the format got messed up when I copy-pasted to
the mail.
/Mar
Reyk Floeter wrote:
> the trunk will use the mac address of it's primary trunkport, which is
> fxp0 in your case. as soon as you add ral0 to the trunk it will also
> use the trunk mac address (00:02:a5:b8:71:b5 from fxp0) for ethernet
> and 802.11 traffic. this should trigger a new authentication
Markus Bergkvist wrote:
I got the feeling that setting up a trunk-interface should be a piece of
cake so I'm probably doing something trivial mistake here. Hopefully
someone can point me to the right direction.
Your interfaces need to be marked up and completely unconfigured.
In your case:
#
hi,
On Tue, Nov 07, 2006 at 10:44:28PM +0100, Markus Bergkvist wrote:
> I try to set up a trunk failover from my fxp0 to my ral0. After the
> trunk is created, trunkport is added and address is assigned I have no
> network connection any longer and I get some strange replies from ping:
>
the t
On Tue, 07 Nov 2006 22:44:28 +0100, Markus Bergkvist <[EMAIL PROTECTED]> wrote:
> I try to set up a trunk failover from my fxp0 to my ral0. After the
> trunk is created, trunkport is added and address is assigned I have no
> network connection any longer and I get some strange replies from ping:
k
I try to set up a trunk failover from my fxp0 to my ral0. After the
trunk is created, trunkport is added and address is assigned I have no
network connection any longer and I get some strange replies from ping:
$ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
ping: sendto: Device
15 matches
Mail list logo
