Discussion
Right - not too good on this networking business
Is there a way to connect two computers to a network, but only have ONE MAC address?
I only have access to one ethernet socket, which is linked to one MAC address. I can change the address its linked to, but it can only handle one MAC address at a time.
I'm thinking a wired router and a couple of lengths of Cat5 may be the answer, but would like confirmation first.
Is there a way to connect two computers to a network, but only have ONE MAC address?
I only have access to one ethernet socket, which is linked to one MAC address. I can change the address its linked to, but it can only handle one MAC address at a time.
I'm thinking a wired router and a couple of lengths of Cat5 may be the answer, but would like confirmation first.
a MAC address is an address that is hard coded into the hardware.. I don't think you'll be able to "spoof" it easily
Wired router with NAT may do the job, but if there is MAC address filtering, you may struggle to get around it.. (let me guess, you're using a cable internet connection??)
slinky
587racing.com
Wired router with NAT may do the job, but if there is MAC address filtering, you may struggle to get around it.. (let me guess, you're using a cable internet connection??)
slinky
587racing.com
Some NICs allow you to modify the MAC, so this is possible, but it's almost always a mistake. What's the *real* problem that the OP is trying to solve? Is it an ISP that only allows one machine to be connected to the network, a cable ISP, perhaps?
In which case, just connect a router to the ISP, which will only see the MAC of the router (MACs are local a LAN) and connect all your PCs to the router.
In which case, just connect a router to the ISP, which will only see the MAC of the router (MACs are local a LAN) and connect all your PCs to the router.
It's a uni network
In which case, just connect a router to the ISP, which will only see the MAC of the router (MACs are local a LAN) and connect all your PCs to the router.
Thats what I was thinking of doing, but would it work in this case as its connecting to a local netwrok, rahter than straight to the net. net access is via a proxy server btw.
zumbruk said:
In which case, just connect a router to the ISP, which will only see the MAC of the router (MACs are local a LAN) and connect all your PCs to the router.
Thats what I was thinking of doing, but would it work in this case as its connecting to a local netwrok, rahter than straight to the net. net access is via a proxy server btw.
Edited by bobthemonkey on Tuesday 7th November 21:11
bobthemonkey said:
I'm thinking a wired router and a couple of lengths of Cat5 may be the answer, but would like confirmation first.
That should work, assuming that the 'security' solution used to prevent more than one PC being connected is as simple as you describe. Another option would/could be to set up internet connection sharing on the PC you use to connect to the network, and then connect the other PC via the first one.
I recon it depends on their reason for implementing this rule.
If it's for useage accounting and basic security then yes, a router should do the trick.
If it's for full on traffic monitoring then a router won't work as the they'll be checking at a packet or datagram level and IIRC the originitaing and destination MACs are carried in the L2 headers so they'll know that it's destined for a machine that isn't your router.
I'd just ask the uni network admins, half the time on uni networks, it's some stupid from above policy that pisses them off as well so they'll be more than happy to tell you the best answer.
If it's for useage accounting and basic security then yes, a router should do the trick.
If it's for full on traffic monitoring then a router won't work as the they'll be checking at a packet or datagram level and IIRC the originitaing and destination MACs are carried in the L2 headers so they'll know that it's destined for a machine that isn't your router.
I'd just ask the uni network admins, half the time on uni networks, it's some stupid from above policy that pisses them off as well so they'll be more than happy to tell you the best answer.
So, basically you have one CAT5 jack on a network.
This port is coded so that only the correct MAC address can pull an IP.
You want to run multiple computers over this network, however you are unable to or unwilling to be perpetually swapping over the registered NIC.
Right. I can, off the top of my head think of two cheap n' cheerful ways of getting around this.
1. But a WiFi AP/Router. Register it's MAC. Tell it to begin NAT/MASQ and DHCP. Fit all of your other machines with WiFi card.
2. Grab a a 486... something old, crappy and can run without a fan (Strap a Socket A cooler to the beast). Fit a dinky little HDD on it and two NIC's (one being the registered unit). Then install Linux via some method which doesn't have it trying to boot a GUI.
Install DHCPCD, DNSMASQ and IPTABLES.
Jot down which network card is which on the system, then configure DHCPCD to pull an IP from the registered NIC. DNSMASQ to handle IP/DNS servives for the other machines, IPTABLES to act as NAT (rusties 3 line MASQ config will do the job).
This port is coded so that only the correct MAC address can pull an IP.
You want to run multiple computers over this network, however you are unable to or unwilling to be perpetually swapping over the registered NIC.
Right. I can, off the top of my head think of two cheap n' cheerful ways of getting around this.
1. But a WiFi AP/Router. Register it's MAC. Tell it to begin NAT/MASQ and DHCP. Fit all of your other machines with WiFi card.
2. Grab a a 486... something old, crappy and can run without a fan (Strap a Socket A cooler to the beast). Fit a dinky little HDD on it and two NIC's (one being the registered unit). Then install Linux via some method which doesn't have it trying to boot a GUI.
Install DHCPCD, DNSMASQ and IPTABLES.
Jot down which network card is which on the system, then configure DHCPCD to pull an IP from the registered NIC. DNSMASQ to handle IP/DNS servives for the other machines, IPTABLES to act as NAT (rusties 3 line MASQ config will do the job).
Re. level 2 headers mentioned earlier, I didn't think NAT worked through encapsulation, I thought the NAT device just keeps a table of mappings? That being the case I think it would fool the average switch's port level security.
Edit: If it doesn't, they make good money on ebay second hand
Edit: If it doesn't, they make good money on ebay second hand
Edited by aldi on Wednesday 8th November 09:18
Mr Beckerman said:
bobthemonkey said:
why do you ask?
Just interested......
University A seems to be far enough away from University B
aldi said:
Re. level 2 headers mentioned earlier, I didn't think NAT worked through encapsulation, I thought the NAT device just keeps a table of mappings? That being the case I think it would fool the average switch's port level security.
MAC addresses never make it off the local LAN. And no, NAT doesn't work by encapsulation, it rewrites the packet headers, and it has nothing to do with MAC addresses anyway.
ThePassenger said:
2. Grab a a 486... something old, crappy and can run without a fan (Strap a Socket A cooler to the beast). Fit a dinky little HDD on it and two NIC's (one being the registered unit). Then install Linux via some method which doesn't have it trying to boot a GUI.
Install DHCPCD, DNSMASQ and IPTABLES.
Jot down which network card is which on the system, then configure DHCPCD to pull an IP from the registered NIC. DNSMASQ to handle IP/DNS servives for the other machines, IPTABLES to act as NAT (rusties 3 line MASQ config will do the job).
Do this. Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff