colinux-users

[coLinux-users] ICS, bridge, Slirp

[Ken P. <ke...@gm...>]

hi,

The ICS, Bridge are forbidden to be used by my company, so I'm trying
to switch to Slirp, but I guess the switch managed by IT will monitor
all network port, if there are two different MAC address out-going
from the same single network port, the port will be disabled
automatically.

How can work around with this policy? and let coLinux works like one
single Mac address?


-- 
perl -e 'print unpack(u,"62V5N\"FME;G\!E<FQ`9VUA:6PN8V]M\"\@``
")'

Re: [coLinux-users] ICS, bridge, Slirp

[Holger K. <hol...@gm...>]

Ken Perl schrieb:
> hi,
> 
> The ICS, Bridge are forbidden to be used by my company, so I'm trying
> to switch to Slirp, but I guess the switch managed by IT will monitor
> all network port, if there are two different MAC address out-going
> from the same single network port, the port will be disabled
> automatically.
> 
> How can work around with this policy? and let coLinux works like one
> single Mac address?

If i understood it right, the mac address of the slirp connection will never show on the 'real' network. This mac address is only seen by colinux. The windows host will 'translate' all packets to his own ip address and send them out on the network with his on mac address in the ethernet frame.

Re: [coLinux-users] ICS, bridge, Slirp

[Ken P. <ke...@gm...>]

yes, I verified, that is true.

On 12/20/06, Holger Krull <hol...@gm...> wrote:
> Ken Perl schrieb:
> > hi,
> >
> > The ICS, Bridge are forbidden to be used by my company, so I'm trying
> > to switch to Slirp, but I guess the switch managed by IT will monitor
> > all network port, if there are two different MAC address out-going
> > from the same single network port, the port will be disabled
> > automatically.
> >
> > How can work around with this policy? and let coLinux works like one
> > single Mac address?
>
> If i understood it right, the mac address of the slirp connection will never show on the 'real' network. This mac address is only seen by colinux. The windows host will 'translate' all packets to his own ip address and send them out on the network with his on mac address in the ethernet frame.
>
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>


-- 
perl -e 'print unpack(u,"62V5N\"FME;G\!E<FQ`9VUA:6PN8V]M\"\@``
")'