On Feb 15, Pekka Savola <[EMAIL PROTECTED]> wrote:
>> [EMAIL PROTECTED]:~# ping6 -c 1 -I eth1 ff02::1
>> connect: Network is unreachable
>
> Maybe 'netstat -gn' could give clues, because you should be receiving a
> response at least from the loopback address. Maybe your loopback
> interface ha
Link-local multicast appears to be broken on some interfaces of some of
my firewalls. I think that this started after I configured quagga's
ospf6d (which does not work because of this), but I am not totally sure.
Does anybody have any idea about how to debug this?
[EMAIL PROTECTED]:~# ping6 -c 1
On May 01, Ben Greear <[EMAIL PROTECTED]> wrote:
> >Can I rely on the presence of the $DEVPATH/driver symlink (e.g.
> >/sys/class/net/eth0/driver) to check if a network interface is a "real"
> >device insteaf of a VLAN or a bridge?
> To distinguish I use a VLAN specific IOCTL (GET_VLAN_REALDEV_NAM
[Please Cc me, I am not subscribed to netdev.]
Can I rely on the presence of the $DEVPATH/driver symlink (e.g.
/sys/class/net/eth0/driver) to check if a network interface is a "real"
device insteaf of a VLAN or a bridge?
- Forwarded message from Marco d'Itri <[EMAIL PRO
On Feb 01, Krzysztof Halasa <[EMAIL PROTECTED]> wrote:
> a) Currently it consists of mid-layer WAN protocols single module (Cisco
>HDLC, FR etc.) + low-level hardware HDLC card driver (C101, N2, PCI200SYN
>etc.). I'm thinking about splitting the protocol module into separate
>modules -
